From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting from cd on an intel 440GX dual processor
Date: Sat, 4 Mar 2006 18:33:20 -0800 [thread overview]
Message-ID: <6da47b5eef218d508e1764275b284734@collyer.net> (raw)
In-Reply-To: <0f4d9df36e260bf20a669d31e65eebca@quanstro.net>
Hmm, so there may be yet another big lump of binary goo that you have
to download into the 960.
The scary size of linux drivers is why I also mentioned the freebsd
driver. I think I saw mention of a netbsd driver too. Maybe they're
smaller.
next prev parent reply other threads:[~2006-03-05 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 2:27 erik quanstrom
2006-03-05 2:33 ` geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-05 2:59 erik quanstrom
2006-03-05 3:19 ` geoff
2006-03-05 1:08 erik quanstrom
2006-03-05 2:11 ` geoff
2006-03-05 22:03 ` Paweł Lasek
2006-03-04 21:02 erik quanstrom
2006-03-04 21:07 ` erik quanstrom
2006-03-04 23:01 ` geoff
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=6da47b5eef218d508e1764275b284734@collyer.net \
--to=geoff@collyer.net \
--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).