Re: 2.6-test11 framebuffer Matrox

[Gábor Lénárt]

On Fri, Dec 19, 2003 at 04:28:01PM +0000, nick black wrote:
> In article <200312190314.13138.schwientek@xxxxxx>, Steffen Schwientek wrote:
> > My Matrox-framebuffer is not working properly. Build direct into the
> > kernel, the monitor will be black with some stripes at startup, just the
> > reset button works.
> > Build as a modules, the same happens if I load the module.
> 
> I've managed to get my AGP G400 working in the following setups under
> 2.6.0 since -test7:
> 
> with Petr's patch, reverting to 2.4 interfaces:
>   video=matroxfb:vesa:0x1bb gives me a great fbcon.  I can either use
>   X's fbdev driver at the same resolution, or the mga driver at any
>   resolution, with no problems.
> 
> without Petr's patch:
>   video=matroxfb:vesa:0x1bb gives me a great fbcon.  I can only use
>   X's fbdev driver at the same resolution; the mga driver at any
>   resolution causes massive console corruption upon switching from X to
>   console and causing any screen changes.  Also, I get a large white
>   block underneath the logo on boot.

Nice. :-) and :-(
With that patch, now I'm happy user of 2.6.0 ;-)
[I was that since 2.6.0-test1, but only on one machine of mine, where fb
 was not important at all]

My only question is: why was fb layer modofied to a state which is UNUSABLE
without a patch which reverts to the 2.4 interface? I'm trying to search
archives and various document, and now I've got the feeling that several
author thinks fbcon only a toy and its ONLY purpose to get the tux logo
on booting. Which is completly false of course ;-(

SORRY (!) if I missunderstood something ...
Or at least please give me some points what is the advantage of the
framebuffer in the state it exists in the official 2.6.0 if it is unusable.
Or maybe I've missed something. My only headache that I would like know
what is the goal with fb in 2.6.x then?

And again: sorry, I would not like to be offensive or something, but I'm
really interested in this topic!
 	
- Gábor (larta'H)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/