public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 25/25] x86: Add a README.x86 for U-Boot on x86 support
Date: Mon, 15 Dec 2014 23:34:57 +0100	[thread overview]
Message-ID: <20141215223457.GF27866@amd> (raw)
In-Reply-To: <1417705450-19867-1-git-send-email-bmeng.cn@gmail.com>

Hi!

> +Status
> +------
> +U-Boot supports running as a coreboot [1] payload on x86. So far only link
> +(Chromebook pixel) has been tested, but it should work with minimal
> adjustments

Link is codeword for Chromebook Pixel? I'd write "Chromebook Pixel
(Link)" if so.

> +on other x86 boards since coreboot deals with most of the low-level details.
> +
> +U-Boot also supports booting directly from x86 reset vector without coreboot,
> +aka raw support or bare support. Currently Google Chromebook link and Intel

Should this me "Chromebook Pixel"?


> +Building rom version U-Boot (hereafter referred to as u-boot.rom) is a little

"ROM version of" ?

> +bit tricky, as generally it requires several binary blobs which are not shipped
> +in the U-Boot source tree. Due to this reason, the u-boot.rom build is not
> +turned on by default in the U-Boot source tree. Firstly, you need turn it on
> +by uncommenting the following line in the main U-Boot Makefile:
> +
> +# ALL-$(CONFIG_X86_RESET_VECTOR) += u-boot.rom
> +
> +Google Chromebook link specific instructions:

"link -> Pixel"?

> +Firstly, you need the following binary blobs:

Firstly->First

> +You can get these binary blobs by:
> +
> +$ git clone http://review.coreboot.org/p/blobs.git
> +$ cd blobs
> +
> +Find the following files:
> +
> +* ./mainboard/google/link/descriptor.bin
> +* ./mainboard/google/link/me.bin
> +* ./northbridge/intel/sandybridge/systemagent-ivybridge.bin
> +
> +The 3rd one should be renamed to mrc.bin.

Should there be instruction where to put those files? Perhaps a script
doing this and getting ROM would be nice?

> +As for the video ROM, you can get it here [2].
> +
> +Now you can build U-Boot and obtain u-boot.rom:

> +$ make chromebook_link_defconfig
> +$ make all
> +
> +Intel Crown Bay specific instructions:
> +
> +U-Boot support of Intel Crown Bay board [3] relies on a binary blob called
> +Firmware Support Package [4] to perform all the necessary initialization steps
> +as documented in the BIOS Writer Guide including initialization of
> the CPU,

"Guide, "


> +Downalod the Intel FSP for Atom E6xx series and Platform Controller

-> Download.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2014-12-15 22:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 15:04 [U-Boot] [PATCH 25/25] x86: Add a README.x86 for U-Boot on x86 support Bin Meng
2014-12-05  0:03 ` Simon Glass
2014-12-05 14:03   ` Bin Meng
2014-12-05 18:34   ` Bruce_Leonard at selinc.com
2014-12-05 19:05     ` Simon Glass
2014-12-05 20:02       ` Bruce_Leonard at selinc.com
2014-12-06  7:52         ` Bin Meng
2014-12-15 22:34 ` Pavel Machek [this message]
2014-12-17  8:13   ` Bin Meng
2014-12-17 14:36   ` Simon Glass

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=20141215223457.GF27866@amd \
    --to=pavel@denx.de \
    --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