From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: For comment: draft BIOS use document for the kernel
Date: 23 Jun 2001 14:26:32 -0600 [thread overview]
Message-ID: <m1u217aqo7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E15DTfd-0003gI-00@the-village.bc.nu>
In-Reply-To: <E15DTfd-0003gI-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> Linux 2.4 BIOS usage reference
Pretty decent. It misses a lot of hardware details that we still
depend on the BIOS to reliably setup for us.
I've got code that does all of this so, setup on a couple of
boards so it should just be a matter of tracking it down and including
it in the documentation.
If there is interest I'll start tracking it down as soon as I have a
free minute.
Eric
next prev parent reply other threads:[~2001-06-23 20:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 16:20 For comment: draft BIOS use document for the kernel Alan Cox
2001-06-22 15:50 ` Rob Landley
2001-06-22 16:32 ` Timur Tabi
2001-06-22 17:11 ` Brad Pepers
2001-06-30 14:47 ` Pavel Machek
2001-07-08 16:59 ` Brad Pepers
2001-06-23 20:26 ` Eric W. Biederman [this message]
2001-06-23 23:58 ` Riley Williams
2001-06-24 1:41 ` D. Stimits
2001-06-25 16:28 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2001-06-22 17:32 Schilling, Richard
2001-06-22 17:42 ` Richard B. Johnson
2001-06-22 17:50 ` Alan Cox
2001-06-22 18:01 ` Richard B. Johnson
2001-06-22 19:05 ` H. Peter Anvin
2001-06-22 21:42 ` Alan Cox
2001-06-30 14:50 ` Pavel Machek
2001-06-22 18:19 ` Brian Gerst
2001-06-22 21:46 ` Alan Cox
2001-06-22 19:24 ` Albert D. Cahalan
2001-06-22 22:09 ` Alan Cox
2001-06-22 17:48 ` Alan Cox
2001-06-22 17:44 Dunlap, Randy
2001-06-22 17:55 ` Alan Cox
2001-06-22 18:25 Comfort, Dan W
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=m1u217aqo7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.