On Thu, 2006-05-18 at 03:07 -0700, Andrew Morton wrote: > Michael Ellerman <[email protected]> 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:
signature.asc
Description: This is a digitally signed message part
- References:
- [RFC/PATCH] Make printk work for really early debugging
- From: Michael Ellerman <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Andrew Morton <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Michael Ellerman <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Andrew Morton <[email protected]>
- [RFC/PATCH] Make printk work for really early debugging
- Prev by Date: Re: 2.6.17-rc2+ regression -- audio skipping
- Next by Date: Re: [RFC/PATCH] Make printk work for really early debugging
- Previous by thread: Re: [RFC/PATCH] Make printk work for really early debugging
- Next by thread: Re: [RFC/PATCH] Make printk work for really early debugging
- Index(es):