[coreboot] Failed to launch windows 7 and two more questions ...

[Boris Shpoungin]

Hi Peter,

Thank you for your response.

Our development board is based on Intel Crown Bay evaluation board with Intel Atom E660 processor and IO Controller Hub EG20T.

Could you recommend Intel board from list of supported ones, which is most
similar to our and could serve as starting point for port?

Boris

--- On Tue, 4/19/11, Peter Stuge <peter at stuge.se> wrote:

> From: Peter Stuge <peter at stuge.se>
> Subject: Re: [coreboot] Failed to launch windows 7 and two more questions ...
> To: coreboot at coreboot.org
> Date: Tuesday, April 19, 2011, 3:23 PM
> Hi Boris,
> 
> Boris Shpoungin wrote:
> > We are considering to use coreboot for our developing
> board.
> 
> Sounds good!
> 
> 
> > I downloaded latest version of coreboot + seabios and
> compiled it
> > for emulation. I tried to launch windows 7 in qemu
> with coreboot
> > bios
> 
> (Note coreboot is not a BIOS. SeaBIOS is the BIOS part.)
> 
> 
> > and got the following error:
> > 
> > "Windows failed to load because the firmware (BIOS) is
> not ACPI
> > compatible"
> > Status: 0xc0000225
> > 
> > Can anyone clarify why I get this error and what i did
> wrong?
> 
> You did nothing wrong. The qemu port of coreboot simply
> does not
> implement ACPI.
> 
> 
> > Could you recommend any manual which describe coreboot
> porting
> > process to new not supported platform? Does it exist
> at all?
> 
> There's nothing really current, because the infrastructure
> in the
> coreboot sources has changed a fair amount since the last
> more
> comprehensive documentation was written.
> 
> The best approach is to look at existing support in
> coreboot for
> hardware similar to yours, and together with firmware
> development
> documentation for the components the way ahead should
> already be
> somewhat clear.
> 
> 
> > Could you provide rough effort estimate to port
> coreboot to new
> > unsupported platform?
> 
> Please define unsupported platform?
> 
> If the significant components are already supported by
> coreboot then
> an experienced coreboot developer with prior knowledge of
> the
> components could accomplish a port in less than a week.
> 
> If no components are supported then an experienced coreboot
> developer
> will spend a minimum of 8 months.
> 
> An experienced firmware developer who knows C but is new to
> coreboot
> would most likely quickly find their way around coreboot.
> 
> A developer with no prior experience from PC firmware
> development nor
> from general C development will spend a lot of time
> learning new
> things.
> 
> 
> //Peter
> 
> -- 
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
>