--=_courier-32621-1046589800-0001-2
Content-Type: multipart/mixed; boundary="UugvWAfsgieZRqgk"
Content-Disposition: inline
--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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=20
> 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=20
wrong to me.
I have attached the fix for the cursor not appearing problem. James=20
already has it in his own tree, why isn't it getting pushed to=20
mainstream?
Regards
Josh
--=20
New PGP public key: 0x27AFC3EE
--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="radeonfb.diff"
Content-Transfer-Encoding: quoted-printable
--- linux/drivers/video/radeonfb.c-2.5.62 2003-01-03 01:31:42.000000000 +01=
00
+++ linux/drivers/video/radeonfb.c 2003-02-18 12:13:07.000000000 +0100
@@ -2212,6 +2212,7 @@
.fb_copyarea =3D cfb_copyarea,
.fb_imageblit =3D cfb_imageblit,
#endif
+ .fb_cursor =3D soft_cursor,
};
=20
=20
--UugvWAfsgieZRqgk--
--=_courier-32621-1046589800-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+YatJT2bz5yevw+4RAtFZAKCqqC0Jw6zI8+ww8qPpffsNToz8tACgz6Jz
VVA9QK+d5evrGVWyKpG8wY8=
=tUtQ
-----END PGP SIGNATURE-----
--=_courier-32621-1046589800-0001-2--