From: Michael Ellerman <michael@ellerman.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [RFC/PATCH] Make printk work for really early debugging
Date: Mon, 22 May 2006 16:40:32 +1000 [thread overview]
Message-ID: <1148280032.24345.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20060518030719.14995317.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Thu, 2006-05-18 at 03:07 -0700, Andrew Morton wrote:
> Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > I'll trawl through the console drivers tomorrow and see if I can guess
> > what percentage look like they will/won't work, then we can decide which
> > way to flip it.
>
> Yes, that's probably safer and saner, thanks. Don't bust a gut over
> it though - it's not your problem and if someone's hurting from it
> then they can write and test the patch.
I had a quick gander at some of the consoles registered under arch. A
lot of them look like they'd be ok running with CON_ANYTIME, ie. they
just write to a fixed address or uart or something simple.
Having said that I still think we should leave this patch as is, and
leave it up to arch people to decide whether they want to add
CON_ANYTIME to their particular console driver.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-05-22 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 9:14 [RFC/PATCH] Make printk work for really early debugging Michael Ellerman
2006-05-18 9:34 ` Andrew Morton
2006-05-18 9:55 ` Michael Ellerman
2006-05-18 10:07 ` Andrew Morton
2006-05-22 6:40 ` Michael Ellerman [this message]
2006-05-18 13:55 ` Andi Kleen
2006-05-18 15:41 ` Michael Ellerman
2006-05-18 16:00 ` Andi Kleen
2006-05-19 4:15 ` Michael Ellerman
2006-05-22 6:57 ` Michael Ellerman
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=1148280032.24345.29.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--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.