All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] default terminals on i386-pc / i386-ieee1275
Date: Sat, 22 Nov 2008 20:57:42 +0100	[thread overview]
Message-ID: <20081122195742.GB7779@thorin> (raw)
In-Reply-To: <491C670F.6050602@nic.fi>

On Thu, Nov 13, 2008 at 07:42:39PM +0200, Vesa Jääskeläinen wrote:
> Robert Millan wrote:
> > Hi,
> > 
> > I think it would be good to make at_keyboard the default input terminal on
> > i386-ieee1275, after the kernel has loaded (via grub-mkconfig).  The AT
> > keyboard is the only choice on OLPC anyway, and avoids ofconsole bugs
> > (this used to be the old behaviour before the terminal split).
> > 
> > Also, I think it would be good to make vga_text the default output terminal
> > on i386-pc, provided that gfxterm auto-setup (in grub-mkconfig.in) wasn't
> > possible.  BIOS output is occasionally buggy (seen in a recent thread), and
> > this way we avoid problems.
> 
> And how does this work with USB keyboards that would be supported by
> BIOS if configured so... ?

On i386-ieee1275, this doesn't really happen, because OFW shuts down USB when
handing control to GRUB.  Note that using at_keyboard was the existing behaviour
up untill recently (it reverted to ofconsole because of the terminal split).

On PC/BIOS, my proposed change would only affect terminal output.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2008-11-22 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 18:11 [PATCH] default terminals on i386-pc / i386-ieee1275 Robert Millan
2008-11-13 17:42 ` Vesa Jääskeläinen
2008-11-22 19:57   ` Robert Millan [this message]

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=20081122195742.GB7779@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.