From: lejatorn@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:30:49 +0200 [thread overview]
Message-ID: <20080610213048.GA4233@oenone.smgl.fr.eu.org> (raw)
In-Reply-To: <cd1b9236a3e898d27b93696e24c9a3e9@quanstro.net>
On Tue, Jun 10, 2008 at 11:27:39AM -0400, erik quanstrom wrote:
> > 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?
>
> yes, if that is the case, you're in a pickle.
>
> however, if you have a place for local nvram and you make sure
> your plan9.ini file (or pxe version thereof) specifies the path to
> the fs, you can still boot to a native usb kbd.
>
> if you can't resolve one of those issues, you will likely need to add
> some code to the init process and link usb/usbd and usb/kb into
> the kernel.
>
> - or - if you have working ethernet, the cec patches that i submitted
> a year or so ago will allow you to enter very early boot information
> using cec(8). i also have a prototype 9load that will also interact
> via cec.
>
> an older version of cec is part of the distribution. my current
> version is in /n/sources/contrib/quanstro/src/cec. i'd be happy to
> put the kernel patches somewhere if folks would find it useful.
Well in my case I am not stuck anymore since I could deal with the nvram
stuff with a usbohci-free kernel. And yeah, I can go back to the regular
kernel if I set the fs path in plan9.ini without the query for it.
I had intially mailed so that if the behaviour qualified as a bug, it
would be reported, and if someone ever stumbled upon the same thing he
could find the quick fix (remove usbohci) if he/she cared enough to
digg in 9fans archives.
Now your solutions are archived as well if needed. ☺
Cheers,
Mathieu.
next prev parent reply other threads:[~2008-06-10 21:30 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
2008-06-10 15:52 ` erik quanstrom
2008-06-10 15:27 ` erik quanstrom
2008-06-10 21:30 ` lejatorn [this message]
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=20080610213048.GA4233@oenone.smgl.fr.eu.org \
--to=lejatorn@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).