| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20080908.164305.140831737.davem@davemloft.net> Date: Mon, 08 Sep 2008 16:43:05 -0700 (PDT) From: David Miller <davem@...emloft.net> To: James.Bottomley@...senPartnership.com Cc: david-b@...bell.net, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC From: James Bottomley <James.Bottomley@...senPartnership.com> Date: Mon, 08 Sep 2008 18:23:06 -0500 > But realistically that's all we need. Our RTC is controlled by two > calls into firmware: a get and a set; nothing else. We don't have the > docs to get at the clock without the firmware calls. I wrote RTC layer drivers on sparc64 that make the firmware calls in the Niagara system case, exactly like your case. Really, this is the way to do this. Since you're not reading what I implemented, I'll read it for you :-/ See drivers/rtc/rtc-sun4v.c, that's the driver Code in arch/sparc64/kernel/time.c creates and registers the appropriate platform_device object once the correct system type is detected, and then rtc-sun4v.c attaches when such objects have been registered. Likewise for all the other RTC types that can be found on Sparc machines. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists