Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o
- To: Horms <horms@debian.org>
- Cc: Sven Luther <sven.luther@wanadoo.fr>, 336450@bugs.debian.org
- Subject: Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o
- From: Sven Luther <sven.luther@wanadoo.fr>
- Date: Mon, 31 Oct 2005 07:57:18 +0100
- Message-id: <20051031065718.GB18046@localhost.localdomain>
- Reply-to: Sven Luther <sven.luther@wanadoo.fr>, 336450@bugs.debian.org
- In-reply-to: <20051031015753.GA7071@verge.net.au>
- References: <20051030222139.5ac3c0b5.dr@jones.dk> <BAY103-F271C920CB526522AD0298CD96D0@phx.gbl> <20051031001330.4278d23f.dr@jones.dk> <20051030234554.GB10278@localhost.localdomain> <20051031015753.GA7071@verge.net.au>
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.
Not sure, i deal in real framebuffer devices, not pale imitations like vesafb
or vga16fb.
Friendly,
Sven Luther
Reply to: