9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] usb: keyboards vs. hubs
Date: Fri,  4 May 2007 08:38:43 -0700	[thread overview]
Message-ID: <13426df10705040838n687987e0nec67036d3e6c2199@mail.gmail.com> (raw)
In-Reply-To: <2d59b7fdf57d18ec73dd5a05cb4aa668@terzarima.net>

On 5/4/07, Charles Forsyth <forsyth@terzarima.net> wrote:
> plan 9 supports the mouse on usb using usb/mouse, running the full protocol,
> so it can find it on the hub.
>
> it does nothing to support the keyboard, so when it works, i'd suspect it's
> because you've enabled legacy mode in the bios, which leaves the keyboard
> in special `boot device mode', and (perhaps depending on which bios)
> that possibly only works when it's directly visible on one of the system's notional root hubs
> (ie, directly wired ports without a hub at all).

and, of course, there's always the issue that many BIOS USB stacks
will support *some*, but not *all*, keyboards. I had this recently
with a brand new Sun Ultra40. No PS/2 keyboards for them, no sir! USB!
It's the 21st century!

So, the hunt for a working USB keyboard turned up several NFG units
and one working unit.

Summary: Just because the BIOS won't support *a* USB keyboard, does
not mean it can not support some other USB keyboard.

Just to keep it interesting.

ron


  reply	other threads:[~2007-05-04 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04  1:58 Lyndon Nerenberg
2007-05-04  6:42 ` Bruce Ellis
2007-05-04 13:08   ` Wes Kussmaul
2007-05-04 14:38     ` Steve Simon
2007-05-04 15:37       ` Wes Kussmaul
2007-05-04  8:24 ` Charles Forsyth
2007-05-04 15:38   ` ron minnich [this message]
2007-05-04  8:45 ` Douglas A. Gwyn

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=13426df10705040838n687987e0nec67036d3e6c2199@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).