From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "J. Mayer" <l_indien@magic.fr>
Cc: Johannes Berg <johannes@sipsolutions.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] booting linux 2.6 in qemu-system-ppc
Date: Mon, 23 May 2005 20:51:02 +1000 [thread overview]
Message-ID: <1116845462.5124.1.camel@gaston> (raw)
In-Reply-To: <1116845275.15980.96.camel@rapid>
On Mon, 2005-05-23 at 12:47 +0200, J. Mayer wrote:
> On Mon, 2005-05-23 at 10:31 +1000, Benjamin Herrenschmidt wrote:
> > > console=ttyS0 console=tty0
> > > Note that the Open-Firmware frame-buffer support is broken in many 2.6
> > > kernels (I mean on real Macs)
> >
> > How so ?
>
> Well, there have been many issues with frame-buffer in 2.6, not only on
> Mac platform.
> With Open-Firmware frame buffer, I remember the first 2.6 kernels had no
> fb output at all.
> Then came kernels that could display a Tux penguin in psychadelic
> colors, I guess it was drawing in 16 bits mode when the OF frame-buffer
> is 15 bits.
> This has been solved in more recent kernels. I don't remember in which
> version it was fixed (but I think around 2.6.5 or 2.6.6).
> I can easily reproduce this on my Ibook and on my Apple Network Server,
> which means it's not a hardware-dependant bug (Ibook 2 has an ATI
> graphic card, ANS is cirrus-logic) nor it's specific to some OF version
> (ANS one is really old...).
>
> There is now another bug with qemu: with recent 2.6 kernels, the
> frame-buffer is recognized and console is working but it only draws
> characters black on black background, even if I send escape sequences to
> change the drawing color. Note that the penguin is well drawn, in those
> cases.
> If you have an idea of what can cause this, I'd be glad to know it ;-)
I would say the palette isn't set properly ...
Ben.
next prev parent reply other threads:[~2005-05-23 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 0:07 [Qemu-devel] booting linux 2.6 in qemu-system-ppc Johannes Berg
2005-05-15 3:41 ` Herbert Poetzl
2005-05-15 9:34 ` Johannes Berg
2005-05-15 12:13 ` J. Mayer
2005-05-15 12:28 ` Johannes Berg
2005-05-16 1:39 ` J. Mayer
2005-05-23 0:31 ` Benjamin Herrenschmidt
2005-05-23 2:58 ` John Reiser
2005-05-23 10:47 ` J. Mayer
2005-05-23 10:51 ` Benjamin Herrenschmidt [this message]
2005-05-25 21:00 ` J. Mayer
2005-05-25 21:46 ` Benjamin Herrenschmidt
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=1116845462.5124.1.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=l_indien@magic.fr \
--cc=qemu-devel@nongnu.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.