From: Paul Mackerras <paulus@cs.anu.edu.au>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: BootX enhancement request
Date: Wed, 25 Aug 1999 14:26:06 +1000 [thread overview]
Message-ID: <199908250426.OAA00893@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.10.9908241456210.17842-100000@mercator.cs.kuleuven.ac.be> (message from Geert Uytterhoeven on Tue, 24 Aug 1999 14:56:45 +0200 (CEST))
Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:
> Thus I can remove the nvram code from atyfb?
Well, what's there doesn't seem to be much use. OTOH, we really do
need something to make it less likely that a newbie will be confronted
by a blank screen because they forgot to put "video=atyfb:vmode:17" in
their kernel command line. Maybe it should look at the registers and
see if the chip is already running, and if so, just use whatever
timings the chip is currently set to (as long as they look sane). Or
maybe there needs to be some intelligence somewhere that looks at the
`compatible' property on the device-tree root node and says "aha, an
iMac, default to 1024x768@75Hz".
I see that there properties called "ATY,DefaultMode" and
"ATY,DisplayMode" on the device-tree node for the ATI chip on my G3
desktop. They both have the value 30 (0x1e). I don't know what mode
30 is.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-25 4:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-24 9:02 BootX enhancement request Benjamin Herrenschmidt
1999-08-24 12:56 ` Geert Uytterhoeven
1999-08-24 13:05 ` Benjamin Herrenschmidt
1999-08-25 4:26 ` Paul Mackerras [this message]
1999-08-25 8:46 ` Geert Uytterhoeven
1999-08-27 6:33 ` Tom Rini
1999-08-27 9:20 ` Benjamin Herrenschmidt
1999-08-28 11:27 ` Geert Uytterhoeven
1999-08-24 17:43 ` David A. Gatwood
1999-08-24 18:21 ` Benjamin Herrenschmidt
1999-08-27 5:46 ` brad allison
-- strict thread matches above, loose matches on Subject: below --
1999-08-24 8:56 Benjamin Herrenschmidt
1999-08-25 3:12 ` David Riley
1999-08-26 0:49 ` Takashi Oe
1999-08-26 2:29 ` Daniel Jacobowitz
1999-08-26 8:39 ` Geert Uytterhoeven
1999-08-26 15:15 ` David Riley
1999-08-22 20:20 Kevin Puetz
1999-08-18 14:33 Is someone working on HFS+ support ? Benjamin Herrenschmidt
1999-08-22 17:45 ` BootX enhancement request brad allison
1999-08-23 13:52 ` Mike Lambert
1999-08-23 16:00 ` Robert Shaw
1999-08-23 20:16 ` brad allison
1999-08-23 20:27 ` Tom Rini
1999-08-23 20:40 ` Robert Shaw
1999-08-23 21:23 ` brad allison
1999-08-23 20:56 ` Jerry Quinn
1999-08-23 21:10 ` David A. Gatwood
1999-08-23 21:27 ` Peter Chang
1999-08-24 4:52 ` Tom Rini
1999-08-23 21:36 ` anthony tong
1999-08-24 4:35 ` Paul Mackerras
1999-08-23 20:29 ` Robert Shaw
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=199908250426.OAA00893@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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 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).