lkml.org 
[lkml]   [2001]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] RTC policy questions
On Sun, Oct 28, 2001 at 05:32:30PM +0100, Alexander Schulz wrote:

> I am currently working on porting the linux kernel to
> the Shark, a StrongARM based computer (DNARD from digital)
> that contains many parts known from PCs.
[snip]
3) Re-write/replace drivers/char/rtc.c in 2.5. This is something I've
been thinking about for a bit because of the number of 'generic' RTC
drivers, and how they only vary slighlty. And then there are some
hw-specific RTC drivers (efirtc.c) which could be modified to be a
personality for the new generic rtc driver. The m68k/APUS version right
now uses a 'mach_hwclk' which handles the actual get/set bits. I
haven't worked out all of the details just yet, but I'm thinking some of
the arch/hw-specific bits will be in a different file and on a per-arch
baises on how mach_hwclk is actually done. Eg PPC would still end up
calling the right ppc_md version, x86 (and default) would yeild the
current behavior.

And this all relates to the original post since we could make sure that
other arches have access to any functions they might need internally.

Is there anyone else out there who's been thinking about reworking the
RTC driver?

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:11    [W:0.056 / U:0.660 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site