From: anthony tong <atong@uiuc.edu>
To: Tom Rini <trini@disparity.net>
Cc: brad allison <jackal@aol.net>,
rshaw@inficad.com, Benjamin Herrenschmidt <bh40@calva.net>,
linuxppc-dev@lists.linuxppc.org, puetzk@iastate.edu
Subject: Re: BootX enhancement request
Date: Mon, 23 Aug 1999 16:36:10 -0500 [thread overview]
Message-ID: <19990823163610.A31129@mango.genunix.net> (raw)
In-Reply-To: <Pine.BSF.3.96.990823162311.86405K-100000@silver.teardrop.net>; from Tom Rini on Mon, Aug 23, 1999 at 04:27:46PM -0400
Tom Rini (Mon, Aug 23, 1999 at 04:27:46PM -0400):
> > I think you missed my point. Don't get me wrong, that's cool to know.
> > But I was thinking more along the lines of a drop down menu to set the
> > resolution from BootX rather than cryptic kernel arguements.
>
> So you want BootX to be able to do what Monitors & Sound can do. Either
> pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
> specify video=aty128fb:1024x768@75 (or so). There is no need for BootX to
> do this.
If you have a version of MacOS that saves the monitor mode in nvram,
you shouldn't need to give any kernel arguments. Alternatively you
can use the linuxpmac tool nvvideo to set this.
It should be simple to add modedb support for the time being as well.
> > It seems the 2.2.10 kernel will not sync to the video settings at all
> > without the kernel arguements.
The default (without kernel arguments) is 640x480-60, unless you have
a video mode already set in nvram.
> What, aty128fb? It's beta and not done. You're prolly better off using
> No Video Driver, unles you're gonna play w/ the source (Anthony, speak up
> if i'm wrong). :)
If it works, use it, if not, send me an email. :)
[[ 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-23 21:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 14:33 Is someone working on HFS+ support ? Benjamin Herrenschmidt
1999-08-18 16:48 ` phandel
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 16:12 ` video driver ( was Re: BootX enhancement request ) john s anderson
1999-08-23 20:16 ` BootX enhancement request 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:21 ` imac exception (Re: BootX enhancement request) Brad Midgley
1999-08-23 21:27 ` BootX enhancement request Peter Chang
1999-08-24 4:52 ` Tom Rini
1999-08-23 21:36 ` anthony tong [this message]
1999-08-24 4:35 ` Paul Mackerras
1999-08-23 20:29 ` Robert Shaw
-- strict thread matches above, loose matches on Subject: below --
1999-08-22 20:20 Kevin Puetz
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-24 9:02 Benjamin Herrenschmidt
1999-08-24 12:56 ` Geert Uytterhoeven
1999-08-24 13:05 ` Benjamin Herrenschmidt
1999-08-25 4:26 ` Paul Mackerras
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
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=19990823163610.A31129@mango.genunix.net \
--to=atong@uiuc.edu \
--cc=bh40@calva.net \
--cc=jackal@aol.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=puetzk@iastate.edu \
--cc=rshaw@inficad.com \
--cc=trini@disparity.net \
/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).