From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Debian GNU/Linux PPC <debian-powerpc@lists.debian.org>,
<ajoshi@unixbox.com>
Subject: Re: [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb
Date: Fri, 28 Dec 2001 12:28:02 +0100 [thread overview]
Message-ID: <20011228112802.11352@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0111281012090.15842-100000@mullein.sonytel.be>
>I _think_ the right solution is to hide the NVRAM vmode/cmode stuff in
>macmodes.c, so all drivers will automagically use it for the default video
>mode.
>
>The same with MAC monitor sense information, just pass it to mac_find_mode().
>
>So mac_find_mode() should do this:
>
> - if default mode specified, try that
> - if MAC monitor sense specified, try that
> - if NVRAM, try that
> - fall back to default mode database walking
No, the NVRAM stuff is driver dependant unfortunately. It's almost common
among drivers for old stuffs like control, chips, etc..., but that is not
the case for recent MacOS drivers. Apple no longer defines a single mode
table, each video driver is now responsible to have it's own mecanism for
that and for storing whatever proprety for saving the mode to nvram. In
fact; the old nvram location is a hack that won't work in all cases as
it's not in xpram any more, it's part of the "device tree extension" part
of the nvram (persistent properties added to selected nodes of the
device-tree).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-28 11:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 21:30 [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb Tom Rini
2001-11-28 9:14 ` Geert Uytterhoeven
2001-12-28 11:28 ` Benjamin Herrenschmidt [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 8:10 Bill Fink
2001-12-02 23:59 ` Benjamin Herrenschmidt
2001-12-03 15:29 ` Tom Rini
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=20011228112802.11352@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=ajoshi@unixbox.com \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).