From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bill Fink <billfink@mindspring.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb
Date: Mon, 3 Dec 2001 00:59:53 +0100 [thread overview]
Message-ID: <20011202235953.3323@smtp.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0112030257230.5627-100000@gwiz.nasa.atd.net>
>> Wasn't there a tool to fiddle and store the vmode/cmode stuff into NVRAM
>> tho which would probably work with all of the other cards?
>
>nvvideo, which could set either a video-mode or a color-mode, but I
>don't think the color-mode was the same thing as the cmode. I had to
>use a color-mode of 3 IIRC (with a video-mode of 18) to get a decent
>display on a 7200 at work (which had a platinum FB IIRC).
Same problem, the information there is driver specific and the
tool currently use a fix offset instead of properly handling the
nvram device tree extension format (afaik). The cmode is also a
driver specific thing and is equivalent to the MacOS driver
"DepthMode" setting, which will map differently to bit depths
depending on the MacOS driver you are dealing with.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-02 23:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 8:10 [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb Bill Fink
2001-12-02 23:59 ` Benjamin Herrenschmidt [this message]
2001-12-03 15:29 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 21:30 Tom Rini
2001-11-28 9:14 ` Geert Uytterhoeven
2001-12-28 11:28 ` Benjamin Herrenschmidt
2001-12-02 16:35 ` Tom Rini
2001-12-01 12:41 ` Martin Costabel
2001-12-02 10:14 ` Paul Mackerras
2001-12-02 21:11 ` Martin Costabel
2001-12-02 22:47 ` Paul Mackerras
2001-12-03 13:16 ` Geert Uytterhoeven
2001-12-03 15:09 ` Tom Rini
2001-12-05 11:22 ` Martin Costabel
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=20011202235953.3323@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=billfink@mindspring.com \
--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).