From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-x86
Date: Sat, 21 Aug 2010 11:42:31 +1000 [thread overview]
Message-ID: <4C6F2F07.9050505@gmail.com> (raw)
In-Reply-To: <AANLkTinxwZ+J=jBFCNXnqGkLsOWjZP_W6R1wkcEfLn3T@mail.gmail.com>
Hi SK,
On 20/08/10 17:42, sk ong wrote:
> Hi,
>
> I notice there is u-boot for x86 architecture in the denx site. I wonder
> whether the u-boot-x86 has the legacy BIOS services, such as dispatching
> PCI/PCIE device option rom such as video, SATA, etc. Does it have int13,
> int15 etc. services for x86 Linux to call during booting phase.
The x86 port has an (extremely) limited BIOS primarily to provide INT12 and
INT15 for the purpose of determining memory size during the Linux Real-Mode
startup procedure.
I don't think that Linux actually needs BIOS other than during the initial
Real-Mode bootstrap. In an embedded environment, the board designer knows
all the information the BIOS would otherwise provide. My goal is to remove
the BIOS functionality from U-Boot and use the Protected-Mode entry point
of the Linux kernel and avoid the switching back-and-forth between Real and
Protected Modes
It sounds like you might be looking at using U-Boot for booting a x86 PC.
If this is the case, maybe you should take a look at coreboot
(http://www.coreboot.org/)
Regards,
Graeme
next prev parent reply other threads:[~2010-08-21 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 7:42 [U-Boot] u-boot-x86 sk ong
2010-08-21 1:42 ` Graeme Russ [this message]
2010-08-22 19:21 ` Robert Schwebel
[not found] ` <AANLkTinh8372fgDaiukRz-+CBS5jYfSNTjvdbK9gR8Xj@mail.gmail.com>
2010-08-25 11:16 ` Graeme Russ
2010-08-25 13:49 ` sk ong
2010-08-25 14:49 ` Graeme Russ
2010-08-25 15:40 ` sk ong
2010-08-27 10:07 ` Detlev Zundel
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=4C6F2F07.9050505@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/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