svn commit: r316642 - head/sys/dev/syscons

Bruce Evans brde at optusnet.com.au
Sun Apr 9 11:09:16 UTC 2017


On Sun, 9 Apr 2017, Andrey Chernov wrote:

> On 09.04.2017 10:33, Bruce Evans wrote:
>> On Sun, 9 Apr 2017, Andrey Chernov wrote:
>>
>>> On 09.04.2017 7:54, Andrey Chernov wrote:
>>>> On 08.04.2017 13:00, Bruce Evans wrote:
>>>>> Log:
>>>>>   Quick fix for removal of the mouse cursor in vga direct graphics
>>>>> modes
>>>>> ...
>>>>
>>>> Please don't forget that this 5 cells range (0xd0-0xd4, last one becomes
>>>> SC_CURSOR_CHAR) can be redefined with "vidcontrol -M", it is needed for
>>>> the case they overlap valid characters region for some code tables.
>>>
>>> Probably we just can change default to remove additional vidcontrol -M
>>> setup. I usually have this range started with 0x03.
>>
>> That can only work if you also avoid 9-bit text modes.  9-bit modes
>> give 1-bit separations between characters, except for those in the
>> graphics range (starting at about 0xd0).
>
> Then let is stays as it is. For me small line in the mouse cursor looks
> less distractive that junk in all 4 chars around, which happens if fonts
> codepage have 0xd0-0xd3 as valid characters.

Both look bad.

Low characters are a better choice if you don't mind the gap, since sc
has too many magic characters whose magic can't be turned off with a
flag line -opost.  These chars are 7-13 and 27.  Also 0 with scteken.
I don't know of any way to reach the glyphs behind these characters
using syscons.

The cursor would have to have to consist of vertical lines of width 2
or more for it to be translatable across all positions (reduce to
width 1 at the gap so that the hardware extends back to width 2).
8x16 doesn't have enough pixels for that.  The border has width 1 in
most places.

Bruce


More information about the svn-src-head mailing list