From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Video subsystem draft
Date: Sun, 27 Nov 2005 04:00:09 +0200 [thread overview]
Message-ID: <43891329.4020003@nic.fi> (raw)
In-Reply-To: <20051126153624.3b4f486f@synapse>
Vincent Pelletier wrote:
> By the way, there is already a font format handled by IEEE1275
> frame buffercards.
> - From the standard :
>
> set-font ( addr width height advance min-char #glyphs -- )
> Set the current font as specified.
>
> So I think they can handle arbitrary-sized glyphs.
> I can't find the font data definition, but as "default-font" returns
> all those values for the default font, reverse engineering will be a
> matter of minutes.
>
> If the font format you want to design could be compatible with ths one,
> it would be a pleasure to port it to sparc :) - and probably the same
> for PPC.
I am not familiar with that, but current implementation only supports
case when grub can read the actual font data itself and render it. So at
this point this is a requirement for graphical console. In principle if
necessary data can be acquired, hardware renderable fonts can be used
but there must be a mechanism to specify viewport that hardware font
rendering checks and does not exceed.
Currently font format itself is open to suggestions and I would like to
hear about possible issues related to some "foreigner" fonts that I
haven't used before. There perhaps are many different kinds of scripts
that might be unreasonable to support but at this point nothing is
dropped out.
next prev parent reply other threads:[~2005-11-27 2:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 11:24 Video subsystem draft Vesa Jääskeläinen
2005-10-23 15:03 ` Timothy Baldwin
2005-10-23 15:24 ` Vesa Jääskeläinen
2005-10-28 3:21 ` Yoshinori K. Okuji
2005-10-28 13:59 ` Vesa Jääskeläinen
2005-11-17 23:19 ` Vesa Jääskeläinen
2005-11-18 11:06 ` Yoshinori K. Okuji
2005-11-22 19:06 ` Vesa Jääskeläinen
2005-11-25 20:25 ` Yoshinori K. Okuji
2005-11-26 0:28 ` Vesa Jääskeläinen
2005-11-26 14:36 ` Vincent Pelletier
2005-11-26 19:54 ` Yoshinori K. Okuji
2005-11-27 1:48 ` Vesa Jääskeläinen
2005-12-09 22:44 ` Marco Gerards
2005-12-10 0:19 ` Yoshinori K. Okuji
2005-12-10 10:31 ` Vesa Jääskeläinen
2005-12-10 21:01 ` Marco Gerards
2005-12-10 21:23 ` Vesa Jääskeläinen
2005-12-10 20:48 ` Vesa Jääskeläinen
2005-12-10 21:15 ` Marco Gerards
2005-12-10 22:14 ` Vesa Jääskeläinen
2005-12-10 22:32 ` Marco Gerards
2005-12-10 23:11 ` Vesa Jääskeläinen
2005-11-27 2:00 ` Vesa Jääskeläinen [this message]
2005-11-26 19:52 ` Yoshinori K. Okuji
2005-11-27 2:09 ` Vesa Jääskeläinen
2005-12-09 22:33 ` Marco Gerards
2005-11-28 21:29 ` Vesa Jääskeläinen
2005-12-06 15:18 ` Vesa Jääskeläinen
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=43891329.4020003@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.