From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usbd problem
Date: Tue, 12 Feb 2008 18:05:25 -0500 [thread overview]
Message-ID: <97e4f83e9cbe0bf0ae23a6de22ee8ee9@plan9.bell-labs.com> (raw)
In-Reply-To: <b678a0515a4b57284acd356e5c86d905@hamnavoe.com>
We added booting via the BIOS to 9load specifically for USB (though it
may have other uses), so that we wouldn't have to add to 9load and
maintain 8,000 lines, and growing, of complex USB code (though that's
likely due to the inherent complexity of USB rather than being the
fault of those who have contributed USB code). See sdB0 and bios0 in
9load(8). The BIOSes have been somewhat uncooperative, but if you
make a USB floppy or USB disk be the first item in your BIOS boot
order, remove
*nobiosload=something
from your plan9.ini, see the example in prep(8) for how to prepare
such a USB disk, and the phase of the moon is right, it should work.
It's worked here for us.
If we get an EHCI driver written, this will all become much more
interesting.
next prev parent reply other threads:[~2008-02-12 23:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 8:21 Richard Miller
2008-02-12 13:21 ` erik quanstrom
2008-02-12 21:24 ` Richard Miller
2008-02-12 21:28 ` geoff
2008-02-12 21:33 ` Richard Miller
2008-02-12 21:37 ` erik quanstrom
2008-02-12 22:18 ` Richard Miller
2008-02-12 23:05 ` geoff [this message]
2008-02-13 6:31 ` arisawa
2008-02-13 8:25 ` Richard Miller
2008-02-13 8:54 ` arisawa
2008-02-13 10:58 ` Richard Miller
2008-02-13 14:13 ` Richard Miller
2008-02-13 18:49 ` geoff
2008-02-13 15:54 ` Richard Miller
-- strict thread matches above, loose matches on Subject: below --
2008-02-12 1:36 erik quanstrom
2008-02-12 8:20 ` Richard Miller
2008-02-12 13:59 ` Sape Mullender
2008-02-12 14:13 ` erik quanstrom
2008-02-12 14:35 ` Sape Mullender
2008-02-12 14:42 ` Fco. J. Ballesteros
2008-02-13 0:50 ` erik quanstrom
2008-02-13 14:32 ` Richard Miller
2008-02-13 14:45 ` erik quanstrom
2008-02-13 14:52 ` Richard Miller
2008-02-13 15:04 ` erik quanstrom
2008-02-13 16:18 ` Sape Mullender
2008-02-13 16:37 ` erik quanstrom
2008-02-13 17:09 ` Sape Mullender
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=97e4f83e9cbe0bf0ae23a6de22ee8ee9@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.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).