Hi Pavel, On Tue, Dec 16, 2014 at 6:34 AM, Pavel Machek <pa...@denx.de> wrote: > 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. >
Most issues fixed in the v4 patch @ http://patchwork.ozlabs.org/patch/422203/, except the Chromebook Pixel (link) issue which will need Simon to comment. Regards, Bin _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot