Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Jan 2017 21:08:23 -0800
From:      Adrian Chadd <adrian.chadd@gmail.com>
To:        Ernie Luzar <luzar722@gmail.com>
Cc:        Kevin Oberman <rkoberman@gmail.com>, Matthias Andree <matthias.andree@gmx.de>,  freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: vt(4) chops off the leftmost three columns
Message-ID:  <CAJ-Vmo=UfpT4FyBX974ijPZL7X16uS-iAZrgkiH9JVE-h2WWTg@mail.gmail.com>
In-Reply-To: <587B0381.5090603@gmail.com>
References:  <CAOtMX2hg%2B-7F10Dx01_0_EzH_Q_eE2J%2B1wWjAiEO7f56ofCLgQ@mail.gmail.com> <CAPyFy2AAWeD-wMCR3aKG8mjPyn_4%2BMzGYBZnYYfddjtHTgDgQQ@mail.gmail.com> <96CA08DF-582A-4405-9E65-B19230EA37DA@gmail.com> <CAOtMX2gBn8iJiCZrzgDCSxBhVN%2B0rjWoXs0YYSNdCLnQwkgAYw@mail.gmail.com> <e85b7e66-6bc4-a8d5-e9be-c9a95c654d32@gmx.de> <CAJ-VmomUChdbFvcpE8xPb=7FX9DftsZQ79B5LYAoyO3wGBw4%2BA@mail.gmail.com> <CAN6yY1swa%2B%2BB3SynQzJ3jAWhKtDKntF0zxsuDZDTODfZWc=ntw@mail.gmail.com> <CAJ-Vmomq4GMkCQexex%2BkacFVytjyVnqppZn3uNEfAmOMTRmeOg@mail.gmail.com> <587B0381.5090603@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
heh.

As always, patches gratefully accepted. :)



-adrian


On 14 January 2017 at 21:07, Ernie Luzar <luzar722@gmail.com> wrote:
>
> You can add these things to the vt to-do list
>
> Change the default font to look like sc.
> Add copy/paste function like sc has.
> Add splash screen support like sc has.
>
>
>
> Adrian Chadd wrote:
>>
>> hi,
>>
>> no, the vt_vga backend doesn't yet do VESA.
>>
>> I keep meaning to sit down and fix this, but life and wifi gets in the
>> way.
>>
>>
>> -adrian
>>
>>
>> On 14 January 2017 at 16:27, Kevin Oberman <rkoberman@gmail.com> wrote:
>>>
>>> On Sat, Jan 14, 2017 at 2:11 PM, Adrian Chadd <adrian.chadd@gmail.com>
>>> wrote:
>>>>
>>>> It depends(tm). I think the VT code just does "640x480x4bpp" and lets
>>>> the BIOS sort it out. A lot of things don't cope well with 640x480
>>>> these days - they try autodetecting picture edges, but a black border
>>>> makes that very difficult.
>>>>
>>>>
>>>> -adrian
>>>
>>>
>>> Can you use vidcontrol(1) to change to something better? 1600x900, maybe?
>>> (Note, I have not tried this and I know that vt does not support a lot of
>>> vidcontrol functionality, but starting X sets the display to 200x56
>>> characters on my laptop.)
>>> --
>>> Kevin Oberman, Part time kid herder and retired Network Engineer
>>> E-mail: rkoberman@gmail.com
>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>>
>>>
>>>> On 14 January 2017 at 08:57, Matthias Andree <matthias.andree@gmx.de>
>>>> wrote:
>>>>>
>>>>> Am 14.01.2017 um 00:11 schrieb Alan Somers:
>>>>>>
>>>>>> I take it back.  The first three columns _are_ rendered, but they
>>>>>> don't show up on some monitiors.  It's as if those monitors require a
>>>>>> minimum amount of overscan on the left side of the screen, and vt(4)
>>>>>> doesn't provide enough.  Can that be tuned?
>>>>>
>>>>> Once upon a time, I've seen similar things on Linux, but with fewer
>>>>> pixels offset, when switching framebuffer drivers - back then, the
>>>>> scanning-VGA-timing was an issue. Is there any way to tweak the row and
>>>>> column timings, with blank periods, viewport offsets and thereabouts?
>
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=UfpT4FyBX974ijPZL7X16uS-iAZrgkiH9JVE-h2WWTg>