9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@9fans.net
Subject: Re: [9fans] usbohci in pccpuf
Date: Tue, 10 Jun 2008 17:39:02 +0200	[thread overview]
Message-ID: <be8a674369bc12ead712c169ed35b82b@lsub.org> (raw)

usb/kb is in sources.
In fact, I'm using that version and not mine. (IIRC).

>  From: uriel99@gmail.com
>  To: 9fans@9fans.net
>  Reply-To: 9fans@9fans.net
>  Date: Tue Jun 10 17:26:38 CET 2008
>  Subject: Re: [9fans] usbohci in pccpuf
>
>  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). So, lets just pretend usb keyboards don't exist (or that all
>  bioses support the 'emulate ancient keyboards' switch and will do so
>  for the rest of eternity).
>
>  uriel
>
>  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:
>  >> >> > Jsyk, I had to comment out usbohci in /sys/src/9/pc/pccpuf for the usb
>  >> >> > keyboard to work with a freshly built 9pccpuf. (there's only usb ports
>  >> >> > on the eserver 325). System pulled last friday (06/06/08).
>  >> >> >
>  >> >> > Cheers,
>  >> >> > Mathieu.
>  >> >>
>  >> >> likely if you turn off "usb legacy" in bios, you will be able to use
>  >> >> the standard kernel.
>  >> >
>  >> > I've just tried, it doesn't seem to change anything on that matter.
>  >> > Well, it's not blocking for me in that case anyway, I can live without
>  >> > usbohci.
>  >>
>  >> 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? Unless there is some place other than
>  > cpurc where I could set those commands?
>  >
>  >
>  >



             reply	other threads:[~2008-06-10 15:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 15:39 Fco. J. Ballesteros [this message]
2008-06-10 15:48 ` Charles Forsyth
2008-06-11  0:51   ` David Leimbach
  -- strict thread matches above, loose matches on Subject: below --
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
2008-06-10 15:52             ` erik quanstrom
2008-06-10 15:27         ` erik quanstrom
2008-06-10 21:30           ` lejatorn

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=be8a674369bc12ead712c169ed35b82b@lsub.org \
    --to=nemo@lsub.org \
    --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).