On Mon, 8 Sep 2003, Petr Vandrovec wrote:
On 7 Sep 03 at 22:58, Dave Jones wrote:
quoted
On Sun, Sep 07, 2003 at 09:51:51PM +0200, cheapisp@sensewave.com wrote:
> The kernel command lines which work with vesafb and matroxfb in 2.4 do not
> work for me in 2.6.0-testX.
>
> kernel (hd0,0)/bz-2.6.0-t4mm3 root=/dev/hdc2 video=matrox:vesa:0x11A
> kernel (hd0,0)/bz-2.6.0-t4mm3 root=/dev/hdc2 vga=794
vga= seems to have changed semantics. (Which is a polite way of saying
"has regressed" IMO), this has been reported several times before, but
it doesn't seem to be too high on peoples 'must fix' list.
> Doing fbset "vesa11A" causes the monitor to lose the sync.
last I looked, fbset needed updates for the changes in 2.6
video= changed sematic too. Now you have to do
video=matroxfb:...., not video=matrox:....
And /dev/fb* changed semantic too, so forget about using fbset on your
box.
I really like to see this fixed. IMHO fbcon should be build on top of fbdev,
not vice-versa.
And whole fb subsystem changed semantic, so do not build both
vesafb & matroxfb into the kernel - either one or another, or
you'll be definitely surprised what will happen (and I'm almost
sure that blank screen is not what you want).
What's wrong with the resource system that prevents this from working?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
On Mon, Sep 08, 2003 at 10:57:34PM +0200, Geert Uytterhoeven wrote:
On Mon, 8 Sep 2003, Petr Vandrovec wrote:
quoted
And whole fb subsystem changed semantic, so do not build both
vesafb & matroxfb into the kernel - either one or another, or
you'll be definitely surprised what will happen (and I'm almost
sure that blank screen is not what you want).
What's wrong with the resource system that prevents this from working?
vesafb ignore failures... for framebuffer it just prints warning only, and
for 0x3C0 region it just completely ignores warning (due to vgacon
clash). But it should not be serious, user should just get console
on matroxfb, and vesafb on /dev/fb1 doing nothing.
Main thing which prevents this from working as users expects is that
modular fbdevs cannot be used by fbcon. So people cannot create
initrd scripts which load proper fbdev driver anymore, after detecting
hardware and making sure that hardware & user wishes & driver are
compatible. They now have to build fbdevs to the kernel, and hope for
the best...
Best regards,
Petr Vandrovec
On Tue, 9 Sep 2003, Petr Vandrovec wrote:
On Mon, Sep 08, 2003 at 10:57:34PM +0200, Geert Uytterhoeven wrote:
quoted
On Mon, 8 Sep 2003, Petr Vandrovec wrote:
quoted
And whole fb subsystem changed semantic, so do not build both
vesafb & matroxfb into the kernel - either one or another, or
you'll be definitely surprised what will happen (and I'm almost
sure that blank screen is not what you want).
What's wrong with the resource system that prevents this from working?
vesafb ignore failures... for framebuffer it just prints warning only, and
for 0x3C0 region it just completely ignores warning (due to vgacon
clash). But it should not be serious, user should just get console
on matroxfb, and vesafb on /dev/fb1 doing nothing.
OK.
Main thing which prevents this from working as users expects is that
modular fbdevs cannot be used by fbcon. So people cannot create
initrd scripts which load proper fbdev driver anymore, after detecting
hardware and making sure that hardware & user wishes & driver are
compatible. They now have to build fbdevs to the kernel, and hope for
the best...
Ugh, didn't know that...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf