Date: Sun, 9 Apr 2017 12:00:43 +0300 From: Andrey Chernov <ache@freebsd.org> To: Bruce Evans <brde@optusnet.com.au> Cc: Bruce Evans <bde@FreeBSD.org>, src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, svn-src-head@FreeBSD.org Subject: Re: svn commit: r316642 - head/sys/dev/syscons Message-ID: <a13f3df4-481d-f4da-2c3f-0733ee76b336@freebsd.org> In-Reply-To: <20170409164754.E1567@besplex.bde.org> References: <201704081000.v38A0dBU078784@repo.freebsd.org> <4a498d83-3b64-18ac-bb0f-890a0c2893fc@freebsd.org> <23b8c635-f856-51b5-a338-d9bb53aefc7c@freebsd.org> <20170409164754.E1567@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a13f3df4-481d-f4da-2c3f-0733ee76b336>