From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status of VGA terminal
Date: Sat, 20 Oct 2007 22:33:49 +0300 [thread overview]
Message-ID: <471A581D.60402@nic.fi> (raw)
In-Reply-To: <20071020192608.GA6128@thorin>
Robert Millan wrote:
> On Sat, Oct 20, 2007 at 10:37:16AM +0300, Vesa Jääskeläinen wrote:
>> Robert Millan wrote:
>>> Hi,
>>>
>>> Anyone knows what's the status of vga.c ? It's currently disabled in the build
>>> system. I reenabled and got it to build again (see attached patch), but it
>>> just displays garbage.
>>>
>>> Is it intended to be integrated with gfxterm?
>> If you want to make video driver for it then and keep it up-to-date,
>> otherwise no. Personally I have no intention to work on it. It displays
>> garbage because font system has changed... and will be changed again in
>> future once there is vector font support. For that I think font blitter
>> goes away and new bitmap blitter (or old one) is used.
>>
>> Question how to scale to different display sizes hasn't been solved
>> either... This is the main reason for vector fonts, scaling bitmap fonts
>> just gets really ugly.
>
> Ok, when I have some time I'll try making it a video driver then.
>
> In the meantime, should we remove it from CVS ? It will have to be removed
> anyway since video drivers don't belong in term/.
Well it is vga terminal :). Implements terminal interface at the moment.
Just being a bit rotten... That is the reason why it is disabled. That
being said, if there would be really a vga video driver then that would
definitely need to be placed elsewhere. If you just remove it from CVS
it will most likely be forgotten and base code will be "lost".
You are of course free to do as you wish with vga terminal. I have no
objections on its removal.
next prev parent reply other threads:[~2007-10-20 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 22:35 status of VGA terminal Robert Millan
2007-10-20 7:37 ` Vesa Jääskeläinen
2007-10-20 19:26 ` Robert Millan
2007-10-20 19:33 ` Vesa Jääskeläinen [this message]
2007-10-21 10:26 ` Marco Gerards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=471A581D.60402@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.