[lkml]   [2001]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [linux-fbdev] [PATCH] matroxfb as a module (PPC)
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

> 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)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.033 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site