From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <97e4f83e9cbe0bf0ae23a6de22ee8ee9@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] usbd problem Date: Tue, 12 Feb 2008 18:05:25 -0500 From: geoff@plan9.bell-labs.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 51aa5686-ead3-11e9-9d60-3106f5b1d025 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.