From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pmac_nvram problems
Date: Sat, 20 Aug 2005 10:03:32 +1000 [thread overview]
Message-ID: <1124496213.5182.87.camel@gaston> (raw)
In-Reply-To: <1124448920.24113.2.camel@localhost>
On Fri, 2005-08-19 at 12:55 +0200, Johannes Berg wrote:
> 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.
Best then is to add a sysdev there so you get suspend() and resume()
notification. You can then write to flash on suspend (same call done by
machine restart/powerdown) and re-read on resume.
Ben.
prev parent reply other threads:[~2005-08-20 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 11:16 pmac_nvram problems Johannes Berg
2005-08-18 5:00 ` Benjamin Herrenschmidt
2005-08-18 13:03 ` Johannes Berg
2005-08-18 21:40 ` Benjamin Herrenschmidt
2005-08-19 10:55 ` Johannes Berg
2005-08-20 0:03 ` Benjamin Herrenschmidt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1124496213.5182.87.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.