From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] usbohci in pccpuf
Date: Tue, 10 Jun 2008 23:41:29 +0800 [thread overview]
Message-ID: <140e7ec30806100841x33ce211dp76c9d44b02a68cce@mail.gmail.com> (raw)
In-Reply-To: <5d375e920806100825w3bbdbfa6h58dd1252c428cd83@mail.gmail.com>
On Tue, Jun 10, 2008 at 11:25 PM, Uriel <uriel99@gmail.com> wrote:
[top-posting fixed]
> On Tue, Jun 10, 2008 at 5:15 PM, <lejatorn@gmail.com> wrote:
>> On Tue, Jun 10, 2008 at 10:17:20AM -0400, erik quanstrom wrote:
>>> you also need to start usb/usbd and usb/kb, at least.
>>
>> yes, but if you need the keyboard to enter stuff during boot time, like
>> the authid, or the path to the filesystem, then it's not possible
>> because I think those choices happen before the point where those
>> commands can be issued, right?
Pretty sure you're right. This situation looks to me like one that
could be avoided by replacing 9load with a proper kernel - otherwise
we'd have to teach 9load about usb, no?
> There is no support for usb keyboards.
>
> Well, nemo implemented it some billions of years ago, and the code is
> bittrotting somewhere in sources (which incidentally is down, as
> usual).
I understand your frustration uriel, but if you read carefully you'll
notice erik's message here makes a reference to usb/kb. Which suggests
to me that usb keyboards have some support nowadays. Some things
change for the better :)
-sqweek
next prev parent reply other threads:[~2008-06-10 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 17:55 lejatorn
2008-06-09 17:56 ` erik quanstrom
2008-06-10 8:36 ` lejatorn
2008-06-10 14:17 ` erik quanstrom
2008-06-10 15:15 ` lejatorn
2008-06-10 15:25 ` Uriel
2008-06-10 15:28 ` erik quanstrom
2008-06-10 15:48 ` sqweek
2008-06-10 15:41 ` sqweek [this message]
2008-06-10 15:52 ` erik quanstrom
2008-06-10 15:27 ` erik quanstrom
2008-06-10 21:30 ` lejatorn
2008-06-10 15:39 Fco. J. Ballesteros
2008-06-10 15:48 ` Charles Forsyth
2008-06-11 0:51 ` David Leimbach
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=140e7ec30806100841x33ce211dp76c9d44b02a68cce@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/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).