This is Radeon 7500 QW on a VT8363/8365 [KT133/KM133 AGP]
Cursor does not appear on console, fbset changes are most likely
to cause screen corruption or just black screen and what must effect all
fb graphics support, choosing an fbdriver and not fb console support, is
an accepted option (at least on menuconfig) having as a result blank
screen on boot.
However, comparing it to 2.4.x, console change between gettys is faster.
# Graphics support
CONFIG_FB=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_RADEON=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
On Sat, Mar 01, 2003 at 04:09:09PM +0000, mk wrote:
> This is Radeon 7500 QW on a VT8363/8365 [KT133/KM133 AGP]
Cool.. I've got a:
radeonfb: ATI Radeon M6 LY DDR SGRAM 32 MB
> Cursor does not appear on console, fbset changes are most likely
> to cause screen corruption or just black screen and what must effect all
> fb graphics support, choosing an fbdriver and not fb console support, is
> an accepted option (at least on menuconfig) having as a result blank
> screen on boot.
Should an fbdriver depend on CONFIG_FRAMEBUFFER_CONSOLE then? It seems
wrong to me.
I have attached the fix for the cursor not appearing problem. James
already has it in his own tree, why isn't it getting pushed to
mainstream?
Regards
Josh
--
New PGP public key: 0x27AFC3EE