Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Geert Uytterhoeven
On Wed, 3 Jan 2001, Petr Vandrovec wrote: > On 3 Jan 01 at 10:54, Tom Rini wrote: > > 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

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Geert Uytterhoeven
On Wed, 3 Jan 2001, Tom Rini wrote: > 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

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Petr Vandrovec
On 3 Jan 01 at 10:54, Tom Rini wrote: > 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. I personally prefer

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Tom Rini
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

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Geert Uytterhoeven
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='

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Petr Vandrovec
On 3 Jan 01 at 10:54, Tom Rini wrote: 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. I personally prefer

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Geert Uytterhoeven
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='

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Tom Rini
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

Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)

2001-01-03 Thread Geert Uytterhoeven
On Wed, 3 Jan 2001, Petr Vandrovec wrote: On 3 Jan 01 at 10:54, Tom Rini wrote: 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