From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PM_TRACE corrupts RTC
Date: Wed, 28 Jun 2006 00:48:08 +0200 [thread overview]
Message-ID: <20060627224808.GA11910@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0606260927130.3747@g5.osdl.org>
On Mon 2006-06-26 09:30:49, Linus Torvalds wrote:
>
>
> On Mon, 26 Jun 2006, Andrew Morton wrote:
> >
> > Oh, I thought it found some spare space in there somehow.
>
> I really tried. The fact is, the RTC chips have at least 114 bytes of
> NVRAM available in them, and most have more. Sadly, while from a hw
> standpoint it's non-volatile, the firmware I was testing with cleared it
> all (including the extended banks etc).
>
> > Making it `default y' was a bit unfriendly. How's about `default n' and
> > `depends on EMBEDDED'?
>
> We can certainly make it 'default n', and perhaps hide it behind
> EXPERIMENTAL (it's not really, but hey..). Not EMBEDDED, though, this is
> literally meant to help random people who have a dead machine on suspend
> be able to just turn this on, test suspend, and then when suspend causes a
> dead machine, just turn off power and reboot immediately again, and it
> will tell you which device was the last one to go through the resume
> cycle.
This should probably be hidden in kernel debugging submenu... or
perhaps even out of the config system. It is only useful if you hack
the .c code, anyway, no?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2006-06-27 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 6:23 Andrew Morton
2006-06-26 15:52 ` Linus Torvalds
2006-06-26 16:14 ` Andrew Morton
2006-06-26 16:30 ` Linus Torvalds
2006-06-27 22:48 ` Pavel Machek [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=20060627224808.GA11910@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®