Hi everyone, are there any functions to convert from and to ISO 8601 formatted timestamps? I found void time_to_tm(time_t totalsecs, int offset, struct tm *result) in include/linux/time.h around line 200, which comes close, but the other way round would be more interesting. regards Dan -- -- Dan Luedtke http://www.danrl.de
Hi all,
I have traced v6_copy_user_highpage_aliasing in arch/arm/mm/copypage-v6.c
and found some questions.
72 /*
73 * Copy the page, taking account of the cache colour.
74 */
75 static void v6_copy_user_highpage_aliasing(struct page *to,
76 struct page *from, unsigned long vaddr)
77 {
78 unsigned int offset = CACHE_COLOUR(vaddr);
79 unsigned long kfrom, kto;
80
I think the following statement is to solve aliasing problem that
kernel & user address map to the same physical frame. When
the kernel mapping is dirty, writing back is needed before the copy_page()
is used. Because the color bit of user space address & kernel one
may be difference which cause inconsistency. Now, the problem is
what is the scenario of dirty cache. When does the PG_dcache_dirty
set ? In normal copy-on-write case, I think the if clause will be false.
81 if (test_and_clear_bit(PG_dcache_dirty, &from->flags))
82 __flush_dcache_page(page_mapping(from), from);
83
The problem is similar with before. Two virtual address map to "to",
in order to avoid the problem that when "kto" is copied with data "kfrom".
The cache data belong to kernel address mapping to "to" will not match
(Continue reading)
Hello, I wrote a virtual timer for a virtual platform. I do not actually have a timer hardware device, but I have a periodic irq that I can use and I know the period which every irq occurs. The result I get is a working clock source, but it is slow. The driver is not %100 right as I have little knowledge of clocksource and clockevents API. Can you help in spotting issues in the below driver? All the numbers are made up :) I would appreciate guidance for what to use on clkrate, cycle value, and any other api parameters. Thanks in advance, Bahadir > /* > * Copyright (C) 2012 B Labs > * > * Virtual timer for linux, mostly written for omap > */ > #include <linux/clk.h> > #include <linux/clocksource.h> > #include <linux/clockchips.h> > #include <linux/err.h> > #include <linux/interrupt.h> > #include <linux/irq.h> > #include <linux/io.h> > > #include <asm/sched_clock.h>(Continue reading)
|
Frankie onuonga requested to add you as a connection on LinkedIn:
Greg,
WHY MIGHT CONNECTING WITH FRANKIE ONUONGA BE A GOOD IDEA? Frankie onuonga's connections could be useful to you After accepting Frankie onuonga's invitation, check Frankie onuonga's connections to see who else you may know and who you might want an introduction to. Building these connections can create opportunities in the future. © 2011, LinkedIn Corporation |
_______________________________________________ Kernel-mentors mailing list Kernel-mentors <at> selenic.com http://selenic.com/mailman/listinfo/kernel-mentors
Send Kernel-mentors mailing list submissions to
kernel-mentors <at> selenic.com
To subscribe or unsubscribe via the World Wide Web, visit
http://selenic.com/mailman/listinfo/kernel-mentors
or, via email, send a message with subject or body 'help' to
kernel-mentors-request <at> selenic.com
You can reach the person managing the list at
kernel-mentors-owner <at> selenic.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernel-mentors digest..."
Today's Topics:
1. tcp/ip (Johan Nestaas)
2. Re: tcp/ip (sumeet gandhare)
----------------------------------------------------------------------
Message: 1
Date: Sun, 15 Jan 2012 02:35:43 -0800
From: Johan Nestaas <johannestaas <at> gmail.com>
To: kernel-mentors <at> selenic.com
Subject: tcp/ip
Message-ID:
<CAA5nq5+A01CBBfgjXtT45a75fZi9edxtRAfy2Xsjhgyf=UfHOQ <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
Sorry if this is too newb of a question for the mailing list, but I tried
the kernelnewbies irc chat and no one was responding. Maybe someone could
direct me to a proper mailing list if this isn't the right place.
I've been trying to follow the latest kernel source of the tcp/ip stack but
I feel overwhelmed and I don't know the best file to start reading from.
Right now I'm reading linux/net/ipv4/af_inet.c but I have a feeling this is
not the best place to start. Does anyone have any suggestions? This would
basically be my start to analyzing the kernel source and operating system
data structures, outside of an Operating Systems class I took a semester
ago.
Thanks,
Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/kernel-mentors/attachments/20120115/0e884139/attachment-0001.html>
------------------------------
Message: 2
Date: Sun, 15 Jan 2012 17:03:35 +0530
From: sumeet gandhare <sumeetgandhare <at> gmail.com>
To: Johan Nestaas <johannestaas <at> gmail.com>
Cc: kernel-mentors <at> selenic.com
Subject: Re: tcp/ip
Message-ID:
<CAGx7bTOWyJoLDQ2JJ3uBzX1W9kEdBbf=RzhjSf2cdhNhKC3Yxg <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
have a look at this link on kernelnewbies
http://kernelnewbies.org/Networking?action=AttachFile&do=get&target=hacking_the_wholism_of_linux_net.txt
HTH,
Regards,
Sumeet
On Sun, Jan 15, 2012 at 4:05 PM, Johan Nestaas <johannestaas <at> gmail.com>wrote:
> Hi,
>
> Sorry if this is too newb of a question for the mailing list, but I tried
> the kernelnewbies irc chat and no one was responding. Maybe someone could
> direct me to a proper mailing list if this isn't the right place.
>
> I've been trying to follow the latest kernel source of the tcp/ip stack
> but I feel overwhelmed and I don't know the best file to start reading
> from. Right now I'm reading linux/net/ipv4/af_inet.c but I have a feeling
> this is not the best place to start. Does anyone have any suggestions? This
> would basically be my start to analyzing the kernel source and operating
> system data structures, outside of an Operating Systems class I took a
> semester ago.
>
> Thanks,
> Johan
>
> _______________________________________________
> Kernel-mentors mailing list
> Kernel-mentors <at> selenic.com
> http://selenic.com/mailman/listinfo/kernel-mentors
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/kernel-mentors/attachments/20120115/eb5b591c/attachment-0001.html>
------------------------------
_______________________________________________
Kernel-mentors mailing list
Kernel-mentors <at> selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
End of Kernel-mentors Digest, Vol 72, Issue 2
*********************************************
_______________________________________________ Kernel-mentors mailing list Kernel-mentors <at> selenic.com http://selenic.com/mailman/listinfo/kernel-mentors
Hi,
_______________________________________________ Kernel-mentors mailing list Kernel-mentors <at> selenic.com http://selenic.com/mailman/listinfo/kernel-mentors
All
I am reading this code in kernel/timer.
my thought is for most of the timer in tv->vec, after cascade they
will stay in the same level.
Am I right?
1014static int cascade(struct tvec_base *base, struct tvec *tv, int index)
1015{
1016 /* cascade all the timers from tv up one level */
1017 struct timer_list *timer, *tmp;
1018 struct list_head tv_list;
1019
1020 list_replace_init(tv->vec + index, &tv_list);
1021
1022 /*
1023 * We are removing _all_ timers from the list, so we
1024 * don't have to detach them individually.
1025 */
1026 list_for_each_entry_safe(timer, tmp, &tv_list, entry) {
1027 BUG_ON(tbase_get_base(timer->base) != base);
1028 internal_add_timer(base, timer);
1029 }
1030
1031 return index;
1032}
I think this function is trying to move some of the timer to another level.
Since the internal_add_timer() will calculate the hash number based on
the timer->expire,
so I guess for the timer which will stay in the same level will not
change their place.
--
--
Wizard
Hello everyone,
I am thinking about a concept for a filesystem (read: kernel-module),
and when studying the sources I found in in include/linux/fs.h
751 struct inode {
...
771 /* Stat data, not accessed from path walking */
772 unsigned long i_ino;
Source: http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=include/linux/fs.h;h=057434af2b900e18745b375b109e52ef03a9c6c0;hb=HEAD#l772
I want to use the blocknumber as inode number to
-keep the code simple
-avoid collisions and
-always know which block of a device an inode can be found in.
When I would my code like intended, and it would be compiled on a 32
bit machine, then unsigned long would be 32 bit. That would cause some
trouble when mounting partitions with more than 2^32 blocks, wouldn't
it?
So, as long as i_ino is not 64 bit (which was already discussed years
ago by some ext4 developers I think), what should I do? Should I
generate inode numbers (e.g. by incrementing a "global" variable) and
check for collisions every time a new inode is allocated?
Are there others ideas? Maybe something using #ifdef-magic?
I want my code to be run also on non-64-bit kernels.
regards,
danrl
--
--
Dan Luedtke
http://www.danrl.de
Hi guys kindly do ignore as I had just gotten a reply the minute i sent this.thanksLa presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.
This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.
From: onuonga <at> live.com
To: kernel-mentors <at> selenic.com
Subject: advice on next step
Date: Fri, 25 Nov 2011 06:26:07 +0000Hi guys,trust you are all well.I was trying to find the document that was being described that is the howto but I can not seem to find it.I was told it contains the information i need to start of.can someone kindly send me the link.thanks,frankieLa presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.
This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.> From: kernel-mentors-request <at> selenic.com
> Subject: Kernel-mentors Digest, Vol 70, Issue 7
> To: kernel-mentors <at> selenic.com
> Date: Thu, 24 Nov 2011 12:00:02 -0600
>
> Send Kernel-mentors mailing list submissions to
> kernel-mentors <at> selenic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://selenic.com/mailman/listinfo/kernel-mentors
> or, via email, send a message with subject or body 'help' to
> kernel-mentors-request <at> selenic.com
>
> You can reach the person managing the list at
> kernel-mentors-owner <at> selenic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kernel-mentors digest..."
>
>
> Today's Topics:
>
> 1. introduction (Frankie Onuong'a)
> 2. Re: introduction (Vijay Kumar)
> 3. Re: introduction (Greg KH)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 24 Nov 2011 08:30:55 +0000
> From: Frankie Onuong'a <onuonga <at> live.com>
> To: <kernel-mentors <at> selenic.com>
> Subject: introduction
> Message-ID: <COL104-W65207413CE94ED4BACC388D0CE0 <at> phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi guys,My name is Frankie Onuonga .I am a student at university taking Computer science and math.
> I am passionate about open source technology.I just waned to introduce myself and ask where does start.
> thanks
> Frankie Onuonga
>
>
> La presente comunicaci?n tiene car?cter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribuci?n, reproducci?n o uso de esta comunicaci?n y/o de la informaci?n contenida en la misma est?n estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicaci?n por error, por favor, notif?quelo inmediatamente al remitente contestando a este mensaje y proceda a continuaci?n a destruirlo. Gracias por su colaboraci?n.This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://selenic.com/pipermail/kernel-mentors/attachments/20111124/6273de38/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 24 Nov 2011 14:28:54 +0530
> From: Vijay Kumar <vijaitm <at> gmail.com>
> To: "Frankie Onuong'a" <onuonga <at> live.com>
> Cc: kernel-mentors <at> selenic.com
> Subject: Re: introduction
> Message-ID:
> <CAEx1gA4Y+QpHub=xvoOY2NPW-TwQDMCkRR+y=pNCYKRN33d4Bw <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Frankie,
>
> Welcome to Opensource World,
>
> regards
> vijay
>
> On Thu, Nov 24, 2011 at 2:00 PM, Frankie Onuong'a <onuonga <at> live.com> wrote:
>
> > Hi guys,
> > My name is Frankie Onuonga .
> > I am a student at university taking Computer science and math.
> >
> > I am passionate about open source technology.
> > I just waned to introduce myself and ask where does start.
> >
> > thanks
> >
> > Frankie Onuonga
> >
> >
> > La presente comunicaci?n tiene car?cter confidencial y es para el
> > exclusivo uso del destinatario indicado en la misma. Si Ud. no es el
> > destinatario indicado, le informamos que cualquier forma de distribuci?n,
> > reproducci?n o uso de esta comunicaci?n y/o de la informaci?n contenida en
> > la misma est?n estrictamente prohibidos por la ley. Si Ud. ha recibido esta
> > comunicaci?n por error, por favor, notif?quelo inmediatamente al remitente
> > contestando a este mensaje y proceda a continuaci?n a destruirlo. Gracias
> > por su colaboraci?n.
> >
> > This communication contains confidential information. It is for the
> > exclusive use of the intended addressee. If you are not the intended
> > addressee, please note that any form of distribution, copying or use of
> > this communication or the information in it is strictly prohibited by law.
> > If you have received this communication in error, please immediately notify
> > the sender by reply e-mail and destroy this message. Thank you for your
> > cooperation.
> >
> > _______________________________________________
> > Kernel-mentors mailing list
> > Kernel-mentors <at> selenic.com
> > http://selenic.com/mailman/listinfo/kernel-mentors
> >
> >
>
>
> --
> ----vijaitm
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://selenic.com/pipermail/kernel-mentors/attachments/20111124/2f1dce0d/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 24 Nov 2011 08:27:20 -0800
> From: Greg KH <greg <at> kroah.com>
> To: Frankie Onuong'a <onuonga <at> live.com>
> Cc: kernel-mentors <at> selenic.com
> Subject: Re: introduction
> Message-ID: <20111124162720.GB4464 <at> kroah.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Nov 24, 2011 at 08:30:55AM +0000, Frankie Onuong'a wrote:
> > I just waned to introduce myself and ask where does start.
>
> Documentation/HOWTO
>
>
> ------------------------------
>
> _______________________________________________
> Kernel-mentors mailing list
> Kernel-mentors <at> selenic.com
> http://selenic.com/mailman/listinfo/kernel-mentors
>
>
> End of Kernel-mentors Digest, Vol 70, Issue 7
> *********************************************
_______________________________________________
Kernel-mentors mailing list
Kernel-mentors <at> selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
_______________________________________________ Kernel-mentors mailing list Kernel-mentors <at> selenic.com http://selenic.com/mailman/listinfo/kernel-mentors
Hi Linux Mentors. I've made a patch to add support of LCD W35i for Mini2440 board. Looks like this is a new version of LCD which is supplied with all new boards. First time I've posted that patch: https://lkml.org/lkml/2011/6/13/345 https://lkml.org/lkml/2011/6/14/331 got comments and fixed all things required to be fixed. I've tried to resend that patch in five months and now I can't get any replies https://lkml.org/lkml/2011/11/17/376 I've formed recipients list from the output of get_maintainer.pl script. This looks like no one is interested in this feature being in mainline? There is no way I can prove that this feature is needed by many users but I've received a letter from someone googled W35i support with a question on how to use that display with Linux. So suggest me please what should I do next? Should I email this path to Andrew Morton for inclusion in -mm three? Or should i just periodically repost that waiting or someone got interested? -- -- Best regards, Denis Kuzmenko.
_______________________________________________ Kernel-mentors mailing list Kernel-mentors <at> selenic.com http://selenic.com/mailman/listinfo/kernel-mentors
RSS Feed2 | |
|---|---|
1 | |
1 | |
8 | |
2 | |
24 | |
15 | |
1 | |
13 | |
12 | |
1 | |
1 | |
4 | |
4 | |
12 | |
1 | |
3 | |
3 | |
10 | |
1 | |
1 | |
9 | |
4 | |
42 | |
9 | |
15 | |
1 | |
6 | |
3 | |
18 | |
2 | |
8 | |
1 | |
9 | |
1 | |
1 | |
2 | |
2 | |
3 | |
2 | |
1 | |
2 | |
3 | |
1 | |
2 | |
7 | |
2 | |
10 | |
21 | |
15 | |
4 | |
3 | |
15 | |
4 | |
16 | |
5 | |
10 | |
45 | |
4 | |
7 | |
16 | |
31 | |
11 | |
4 | |
14 | |
7 | |
6 | |
2 | |
2 | |
18 | |
55 | |
26 | |
77 | |
119 | |
20 |
