From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fixed ieee1275 console
Date: Thu, 11 Oct 2007 16:01:35 +0200 [thread overview]
Message-ID: <20071011140135.GA19873@thorin> (raw)
In-Reply-To: <8a2a06bb0710101457g5b3e4a19v65025a0e017f3d73@mail.gmail.com>
On Wed, Oct 10, 2007 at 11:57:44PM +0200, Marcin Kurek wrote:
> > In your code there's a condition in which _serial is set to 0 and _fb is
> > left unset (as 0). Is this intended? Sounds like a bug.
>
> Not this is not a bug. We can heve 3 cases here:
>
> 1) True serial console. In this case recent versions of OF set stdout
> name and type to "serial" (_serial = 1, _fb = 0) In this case we want
> to use simple frames.
>
> 2) On the screen terminal without framebuffer (fb-mode not existing or
> set to 0x0x0) In this case we will get type "serial" (As it not
> supports pixel operations) and name "display" as this is not real
> serial console. (_serial = 0, _fb = 0) In this case we can use cp437
> frames.
>
> For old versions of OF this case need to catch "bootconsole" too.
>
> 3) Console with framebuffer (fb-mode != 0x0x0) In this case we will
> get type to "display" or "vga" (_serial = 0, _fb = 1) In this case we
> can not use cp437 frames as vga font used by OF maps only first 127
> characters ;( I put this in to separate case as we can still use
> framebuffer interface to draw some frames or try to load a working
> font, etc.
>
> I use 'true serial' as a safe default if detection fails for some reasons.
Ok but do we really need to make that distinction? Perhaps it would be simpler
to define a structure that only cares about charset capability, and make code
that plays with charsets just check that, without caring if it's a serial
cable or a vga with old firmware, etc.
And possibly this could be integrated with your proposed use of
grub_term.flags ? (I'm not sure if that would make sense, but it would be
nice to simplify if possible)
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-10-11 14:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 10:57 [PATCH] Fixed ieee1275 console Marcin Kurek
2007-10-01 12:31 ` Robert Millan
2007-10-01 12:33 ` Robert Millan
2007-10-01 18:14 ` Marcin Kurek
2007-10-01 18:39 ` Robert Millan
2007-10-01 19:43 ` Marcin Kurek
2007-10-02 21:39 ` Robert Millan
2007-10-03 23:33 ` Marcin Kurek
2007-10-04 20:50 ` Robert Millan
2007-10-10 15:11 ` Marcin Kurek
2007-10-10 19:19 ` Robert Millan
2007-10-10 21:57 ` Marcin Kurek
2007-10-11 14:01 ` Robert Millan [this message]
2007-10-11 15:06 ` Marco Gerards
2007-10-12 16:16 ` Marcin Kurek
2007-11-10 17:05 ` Marco Gerards
2007-11-11 11:02 ` Marcin Kurek
2007-11-18 11:37 ` Marco Gerards
2007-10-15 20:43 ` Marcin Kurek
2007-11-18 13:18 ` Marco Gerards
2007-11-18 12:11 ` 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=20071011140135.GA19873@thorin \
--to=rmh@aybabtu.com \
--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.