From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: tbm@cyrius.com, linux-mips@linux-mips.org,
manoj.ekbote@broadcom.com, mark.e.mason@broadcom.com
Subject: Re: BigSur: garbled characters during boot
Date: Sun, 25 Nov 2007 23:17:17 +0100 [thread overview]
Message-ID: <20071125221717.GA11406@alpha.franken.de> (raw)
In-Reply-To: <20071125.222803.25909189.anemo@mba.ocn.ne.jp>
On Sun, Nov 25, 2007 at 10:28:03PM +0900, Atsushi Nemoto wrote:
> Do you enable EARLY_PRINTK? If so, this might be the console-handover
> issue. On the handover, "console handover: boot ..." message will be
> printed both early console and new console. If they were same device,
> drivers might be confused.
it will not be printed on both consoles, but while early console is
active the real console driver does things to the serial chip,
which might confuse the early console driver/prom.
> IIRC Maciej have tried to fix this issue a while ago on LKML.
this didn't work out for ip22zilog, so I digged through the mess. I
solved the problem by setting up the chip in one go. Before there
was some chip setup during probing, which killed prom_putchar().
Thomas
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2007-11-25 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 12:48 BigSur: garbled characters during boot Martin Michlmayr
2007-11-25 13:28 ` Atsushi Nemoto
2007-11-25 13:43 ` Martin Michlmayr
2007-11-26 11:34 ` Maciej W. Rozycki
2007-11-25 22:17 ` Thomas Bogendoerfer [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=20071125221717.GA11406@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=manoj.ekbote@broadcom.com \
--cc=mark.e.mason@broadcom.com \
--cc=tbm@cyrius.com \
/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