On Mon, Oct 31, 2005 at 04:43:57PM +0900, Horms wrote: > On Mon, Oct 31, 2005 at 07:57:18AM +0100, Sven Luther wrote: > > On Mon, Oct 31, 2005 at 10:57:54AM +0900, Horms wrote: > > > > Vesafb is no more modular now, and should either have been dropped > > > > fully or > > > > builtin, please check the config file. > > > > > > As the driver is no longer modular it is now built into the kernel > > > on all i386 and amd64 architectures. It is not included > > > in any other achitecture, but I believe this was the case > > > when it was modular. > > > > > > # grep -r VESA debian/arch/ | grep -v .svn > > > debian/arch/i386/config:CONFIG_FB_VESA=y > > > debian/arch/amd64/config:CONFIG_FB_VESA=y > > > > > > The reason that it has been changed from modular to builtin, > > > is that making it modular was a somewhat problematic patch. > > > I hope we can find a solution that doesn't lead us back to > > > that code. > > > > Still, i don't think its modular vs builtin nature should change things, > > except if some stuff noz use vesafb, while vga16fb was used previously. > > I wouldn't have thought so either, but the problems seem to > have appeared at about the same time that the change was > made (2.6.13), so I suspect a link.
Well, i don't know this stuff very well, but i kind of get the impression that previous vga=xxx calls used the vga16fb fbdev, while it now gets to use vesafb. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
