Re: [RFC/PATCH] Make printk work for really early debugging

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 guess many people are using earlyprintk or console=uart..
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC/PATCH] Make printk work for really early debugging
    • From: Michael Ellerman <[email protected]>

• 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]>

• Prev by Date: Re: [RFC/PATCH] Make printk work for really early debugging
• Next by Date: [patch] fix magic sysrq on strange keyboards
• 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):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]