From: Tom Rini <trini@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-fbdev@vuser.vu.union.edu, linux-kernel@vger.kernel.org
Subject: Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)
Date: Wed, 3 Jan 2001 10:54:52 -0700 [thread overview]
Message-ID: <20010103105452.X26653@opus.bloom.county> (raw)
In-Reply-To: <20010103091613.Q26653@opus.bloom.county> <Pine.LNX.4.05.10101031840410.611-100000@callisto.of.borg>
In-Reply-To: <Pine.LNX.4.05.10101031840410.611-100000@callisto.of.borg>; from geert@linux-m68k.org on Wed, Jan 03, 2001 at 06:44:59PM +0100
On Wed, Jan 03, 2001 at 06:44:59PM +0100, Geert Uytterhoeven wrote:
> On Wed, 3 Jan 2001, Tom Rini wrote:
> > Third, the nvram_read_byte needs to be protected by CONFIG_NVRAM.
>
> I'd really like to move the nvram part to mac_fb_find_mode() in macmodes.c, so
> it will work automagically for all drivers on PowerMac.
>
> I'd also like to remove the `vmode' and `cmode' `video=' arguments, in favor of
> the archictecture-neutral `<xres>x<yres>[-<bpp>][@<refresh>]' and
> `<name>[-<bpp>][@<refresh>]' arguments (which already work on mac, BTW).
Quite wonderfully, almost. My monitor (ViewSonic G810) claims it can do
1280x1024@90, but when i boot with that on my x86 box, it comes up at 87.5
or so (and shifted to the left ~1 penguin). But anyways..
> You can already use `mac<vmode>' instead of `vmode:<vmode>'.
Ah, is this documented anywhere? I'm sure it'd make some peoples life
easier.
> IMHO, the less PowerMac-specific code in _each_ driver, the better.
I agree this sounds good. I just think it's too late to do it now. :)
The vmode/cmode/vesa number stuff should stick around in 2.4 (it's too late
now to remove it) but documented as obsolete, and removed in 2.5.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-03 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 16:16 Tom Rini
2001-01-03 17:44 ` [linux-fbdev] " Geert Uytterhoeven
2001-01-03 17:54 ` Tom Rini [this message]
2001-01-03 22:21 ` Geert Uytterhoeven
2001-01-03 19:25 Petr Vandrovec
2001-01-03 22:24 ` Geert Uytterhoeven
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=20010103105452.X26653@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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
all inboxes | Powered by JetHome®