Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jan 2017 23:13:46 +0000
From:      Anindya Mukherjee <anindya49@hotmail.com>
To:        Adrian Chadd <adrian.chadd@gmail.com>
Cc:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   RE: vt(4) chops off the leftmost three columns
Message-ID:  <BN6PR22MB08029ABD070FB0CFC1A92856B6700@BN6PR22MB0802.namprd22.prod.outlook.com>
In-Reply-To: <CAJ-Vmo=bRJvkX9JM0CmLcQexpPF%2B6X8GDB3urCTjAAS6Tzro1Q@mail.gmail.com>
References:  <BN6PR22MB0802DB657D97A1F6C8EB3F34B67E0@BN6PR22MB0802.namprd22.prod.outlook.com>, <CAJ-Vmo=bRJvkX9JM0CmLcQexpPF%2B6X8GDB3urCTjAAS6Tzro1Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks! I needed a breakdown like this. I'll need to study the code a bit m=
ore.

Anindya
________________________________________
From: Adrian Chadd [adrian.chadd@gmail.com]
Sent: January 20, 2017 3:11 PM
To: Anindya Mukherjee
Cc: freebsd-current@freebsd.org
Subject: Re: vt(4) chops off the leftmost three columns

hiya,

Mechanically it doesn't look /that/ hard:

* vesa.ko pulls in the vesa.c bits and the syscons vesa control bits.
Ideally we'd have them as two separate modules, so you could load
"vesa" without needing the syscons bits.
* Maybe then write a vt 'fb' interface to talk to the old-school
framebuffer interface
* Then (if we're lucky) we can have vt use the same VGA, VESA, (mach,
creator, etc!) through the fb interface, rather than reimplementing
its own.

I looked at it and it doesn't look /that/ hard. If you only cared
about vesa, then you could do something like what 'creator' and
'creator_vt' did in sys/dev/fb/ . It's just sad that the vt interface
to the screen buffer isn't as complete as the older school framebuffer
interface is.


-adrian


On 19 January 2017 at 12:35, Anindya Mukherjee <anindya49@hotmail.com> wrot=
e:
> Hi Adrian,
>
> I was looking at the source for the vt driver. Wondering how much work it=
 is to add VESA support to the VGA backend? As you say ATM it's hardcoded t=
o use 640x480. Pardon my ignorance, but can we reuse any VESA code from sys=
cons?
>
> Also, how dependent is splash/screensaver support on the VESA implementat=
ion?
>
> Thanks,
> Anindya



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BN6PR22MB08029ABD070FB0CFC1A92856B6700>