vgafb is evil and when its compiled in, video modes with 50 or more
lines doesn't work (but 80x43 does).
This has led to lots on confusion for various people (including
myself) as to why 80x50 doesn't work, when 80x43 does, why GPM
doesn't work with scroll-back properly, etc. and much noise on the
list.
Anyhow, vgacon works and vgafb should be depreciated and removed
before the freeze otherwise there will be thousands of questions to
this list ask "why vga=ext doesn't work?"
This isn't the `right fix' obviously, but it keeps the patch sizes
down.
-cw
--p4qYPpj5QlsIQJ0K
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="linux-2.1.a00144.116-console-fix"
--- drivers/video/Config.in.orig Thu Aug 20 11:29:47 1998
+++ drivers/video/Config.in Thu Aug 20 11:30:07 1998
@@ -50,12 +50,12 @@
fi
# I used CONFIG_ARM here because the ARCH construct doesn't seem to work
# with xconfig. --pb
- if [ "$ARCH" = "i386" -o "$ARCH" = "alpha" -o "$ARCH" = "ppc" -o \
- "$CONFIG_ARM" = "y" ]; then
- if [ "$CONFIG_ARM" != "y" -o "$CONFIG_ARCH_ACORN" != "y" ] ; then
- tristate 'VGA chipset support (text only)' CONFIG_FB_VGA
- fi
- fi
+# if [ "$ARCH" = "i386" -o "$ARCH" = "alpha" -o "$ARCH" = "ppc" -o \
+# "$CONFIG_ARM" = "y" ]; then
+# if [ "$CONFIG_ARM" != "y" -o "$CONFIG_ARCH_ACORN" != "y" ] ; then
+# tristate 'VGA chipset support (text only)' CONFIG_FB_VGA
+# fi
+# fi
if [ "$ARCH" = "alpha" ]; then
tristate 'TGA framebuffer support' CONFIG_FB_TGA
fi
--p4qYPpj5QlsIQJ0K--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html