From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-pm@lists.osdl.org, Nigel Cunningham <ncunningham@linuxmail.org>
Subject: Re: [PATCH 1/2] Add some basic resume trace facilities
Date: Fri, 16 Jun 2006 11:49:13 +1000 [thread overview]
Message-ID: <1150422553.7725.92.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131551210.5498@g5.osdl.org>
On Tue, 2006-06-13 at 15:59 -0700, Linus Torvalds wrote:
> The Apple Mac Mini I can't even get to _beep_, which is really annoying.
> It's a wonderful debug sequence ("oh, I head 15 beeps, it got to point
> X"). Or rather, it's "wonderful" compared to something that gives you just
> one single piece of data after the reboot ;)
No magic GPIO or ACPU command you can use to tweak the front led ?
> The real-time clock was literally the only thing I could find that didn't
> get cleared, and that obviously has some serious limitations size-wise.
What about vram ? the entire of it gets cleared or only the displayed
part ?
Ben.
next prev parent reply other threads:[~2006-06-16 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 22:25 [PATCH 1/2] Add some basic resume trace facilities Gross, Mark
2006-06-13 22:59 ` Linus Torvalds
2006-06-13 23:04 ` Dave Jones
2006-06-13 23:13 ` Linus Torvalds
2006-06-16 1:49 ` Benjamin Herrenschmidt [this message]
2006-06-16 3:08 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-06-13 21:30 [PATCH 0/2] suspend-to-ram debugging patches Linus Torvalds
2006-06-13 21:35 ` [PATCH 1/2] Add some basic resume trace facilities Linus Torvalds
2006-06-13 22:10 ` Nigel Cunningham
2006-06-13 22:50 ` Linus Torvalds
2006-06-14 10:25 ` Pavel Machek
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=1150422553.7725.92.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@linuxmail.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