[lkml]   [2006]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: NTP time sync
> -----Original Message-----
> From:
> [
>] On Behalf Of David Brownell
> Sent: den 26 november 2006 00:22
> To: Benjamin Herrenschmidt
> Cc:; Alessandro Zummo;;
>; Linux Kernel Mailing List;
>; Andi Kleen;;
> Subject: Re: NTP time sync
> On Thursday 23 November 2006 3:00 am, Benjamin Herrenschmidt wrote:
> >
> > Couldn't we have a transition period by making the kernel
> not rely on
> > interrupts ? if the NTP irq code just triggers a work
> queue, then all of
> > a sudden, all of the RTC drivers can be used and the
> latency is small.
> > That might well be a good enough solution and is very simple.
> Good point. Of course, one issue is that the NTP sync code all
> seems to be platform-specific right now ... just like the code
> to set the system time from an RTC at boot (except for the new
> RTC framework stuff) and after resume.
> - Dave

Looking at rtc-dev.c I don't see a MARJOR number assigned to /dev/rtcN. Seems like
it is dynamically allocated to whatever major number that is free.
Is that the way it is supposed to be? How do I create a static /dev/rtcN in my /dev
directory if the major number isn't fixed?
Maybe I am just missing something, feel free to correct me :)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-11-26 12:07    [W:0.039 / U:3.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site