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
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
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
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
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='
Hello all. I've recently been playing with modules on my PPC system, and
noticed that matroxfb doesn't work as a module, because of mac_vmode_to_par.
But, after looking at other drivers which did work (aty and aty128) I noticed
matroxfb was doing something it didn't need to be doing.
First, the
Hello all. I've recently been playing with modules on my PPC system, and
noticed that matroxfb doesn't work as a module, because of mac_vmode_to_par.
But, after looking at other drivers which did work (aty and aty128) I noticed
matroxfb was doing something it didn't need to be doing.
First, the
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
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='
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
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
11 matches
Mail list logo