On Fri, 2005-08-19 at 07:40 +1000, Benjamin Herrenschmidt wrote: > Just a question: Why do you want to have the nvram low level code as a > module ? It's sort-of an intergral part of the arch code ... Because I Can (TM). Actually, I just did this because of the suspend issue where OSX would reset some values (notably the boot sound volume), but Linux wouldn't see this. So I figured that if I can compile it as a module (the Kconfig option is a tristate after all) I could just unload it. But that failed because of the alloc_bootmem issue. I wouldn't mind having it built-in at all, if it would re-read the cached values when resuming from suspend. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: pmac_nvram problems
- From: Benjamin Herrenschmidt <[email protected]>
- Re: pmac_nvram problems
- References:
- pmac_nvram problems
- From: Johannes Berg <[email protected]>
- Re: pmac_nvram problems
- From: Benjamin Herrenschmidt <[email protected]>
- Re: pmac_nvram problems
- From: Johannes Berg <[email protected]>
- Re: pmac_nvram problems
- From: Benjamin Herrenschmidt <[email protected]>
- pmac_nvram problems
- Prev by Date: Re: 2.6.13-rc6-rt9
- Next by Date: Re: Multiple virtual address mapping for the same code on IA-64 linux kernel.
- Previous by thread: Re: pmac_nvram problems
- Next by thread: Re: pmac_nvram problems
- Index(es):