Mailinglist Archive: radeonhd (290 mails)

[bugzilla-daemon@xxxxxxxxxxxxxxx]

http://bugs.freedesktop.org/show_bug.cgi?id=16969





--- Comment #4 from Egbert Eich <eich@xxxxxxxxxxxxxxxxxxx>  2008-08-11 00:52:08 
PST ---
(In reply to comment #3)
> Luc Verhaegen said that this only happens on cards and IGPs with broken BIOS,
> not all of them, but fixing it won't be a problem since we already do a sanity
> check beofre applying any hacks, so non-broken cases won't be affected.
>
> Egbert, what board do you have?
I don't think that's the reason.
Since VGA has its own VGAHDP we should not compare the VGAHDP address to the
HDP address but the the MC_FB_LOCATION (or a comparable register on later
hardware). The reason why most people are not seeing this bug is because the
kernel restores everything. I cannot even see a restore problem when I
completely disable VGA save/restore. This is because the Linux kernel does font
save restore as well as repaint the screen.
Looking at the screen shot suggests the following: the space character in the
font data is broken while the fonts are ok?
What do you get when you type on the console? Does a space also produce a
broken character?
What happens when you do 'setfont' on the console?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
xorg-team mailing list
xorg-team@xxxxxxxxxxx
http://lists.x.org/mailman/listinfo/xorg-team
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx