From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot for x86 Core2Duo target
Date: Mon, 21 Feb 2011 09:46:00 -0000 [thread overview]
Message-ID: <006401cbd1ac$26e36d10$74aa4730$@pont@sdcsystems.com> (raw)
In-Reply-To: <8337A7BEA7354407900A21CD5E18A7BB@zvi44e931d542f>
Zvi wrote...
> On my next project, the target is Core2Duo (AMPRO's COM840).
>
> Is it a wise decision to use u-boot on this target ?
Probably not!
Ampro will already have invested a lot of time and effort in porting the
BIOS to that board and are giving you a device that works out of the box.
If there is a specific issue that you have with their board then talk to
Ampro and they may look into it for you.
> Is it a huge project to port it to another x86 target that has a different
> ethernet controller ?
In the first instance it will rely on you being able to get all of the
information that you need in order to initialise all of the respective
hardware and some of the x86 CPU and chipset vendors limit who they make it
available to.
There are other questions you will need to ask, for instance. Are you using
the VGA display? If so, will your operating system device driver work
without the video BIOS having done the initialisation or some of the other
services provided by it?
> The u-boot image is loader by the BIOS from compact flash via SATA.
As Graeme Russ said, U-Boot would replace the BIOS. I haven't looked at the
board but I would assume the BIOS can be in-situ updated. In the first
instance you could try the flash update utility that goes along with the
BIOS to see if it will reprogram it with an arbitrary binary. It may not do
as it may have a write protected boot block that you can't replace.
Andy.
prev parent reply other threads:[~2011-02-21 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 0:04 [U-Boot] u-boot for x86 Core2Duo target Zvi Vered
2011-02-19 3:17 ` Graeme Russ
2011-02-21 9:46 ` Andy Pont [this message]
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='006401cbd1ac$26e36d10$74aa4730$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.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