From: "Matt Sealey" <matt@genesi-usa.com>
To: "'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, 'Nathan Lynch' <ntl@pobox.com>
Subject: RE: OpenFirmware framebuffer
Date: Wed, 14 Jun 2006 09:07:41 -0500 [thread overview]
Message-ID: <00b601c68fbb$e9c2c570$99dfdfdf@bakuhatsu.net> (raw)
In-Reply-To: <1150242815.13958.71.camel@localhost.localdomain>
> Send us a copy of your dmesg log. Also, does the pegasos
> firmware creates a "display" node in OF with the right type
> and properties ?
dmesg log might be a bit clumsy to get but I will try.
Please tell me what the display node should have? I can check that. I
am curious though as it does seem to have worked.. it uses the mode I
set in firmware, cleans the screen and prints a message to display..
just not MUCH of a message. With previous "broken" firmware and kernels
I would get a garbage screen with the chrp_boot messages on it, but
yesterday this new message (welcome to Linux.. MSR, HID0 printout) was
a welcome change, but.. not a console so much as "not a blank screen".
dmws2: the current released firmware doesn't. But I get to test out all
these new broken features.. :3
--
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
next prev parent reply other threads:[~2006-06-14 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 15:26 OpenFirmware framebuffer Matt Sealey
2006-06-13 16:11 ` Nathan Lynch
2006-06-13 16:27 ` Matt Sealey
2006-06-13 23:53 ` Benjamin Herrenschmidt
2006-06-14 14:07 ` Matt Sealey [this message]
2006-06-14 14:29 ` Benjamin Herrenschmidt
2006-06-14 16:02 ` Matt Sealey
2006-06-13 21:33 ` David Woodhouse
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='00b601c68fbb$e9c2c570$99dfdfdf@bakuhatsu.net' \
--to=matt@genesi-usa.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.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;
as well as URLs for NNTP newsgroup(s).