We are considering to use coreboot for our developing board.
I downloaded latest version of coreboot + seabios and compiled it for emulation. I tried to launch windows 7 in qemu with coreboot bios 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?
Two more questions:
Could you recommend any manual which describe coreboot porting process to new not supported platform? Does it exist at all?
Could you provide rough effort estimate to port coreboot to new unsupported platform?
Thank you.
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
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@stuge.se wrote:
From: Peter Stuge peter@stuge.se Subject: Re: [coreboot] Failed to launch windows 7 and two more questions ... To: coreboot@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@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
* Boris Shpoungin wmk587@yahoo.com [110419 23:31]:
Could you recommend any manual which describe coreboot porting process to new not supported platform? Does it exist at all?
The Wiki is an excellent source of information.
Could you provide rough effort estimate to port coreboot to new unsupported platform?
That incredibly depends on the porter's skill set. However, I have seen the following times to be accurate in some cases.
New mainboard: ~ 1 person month (assuming you want features like ACPI, S3, ...) This can vary a lot between 1 day and many weeks
New cpu / chipset: ~ 6 - 12 person months
These estimates obviously don't include the time you need to obtain the documentation for your chipset, which in some cases can take several months, too.
Stefan
Hi Stefan,
Thank you for your response.
What is the Wiki you mentioned in your mail? So far, I've found only three pieces of information on coreboot web site:
http://www.coreboot.org/Documentation http://qa.coreboot.org/docs/doxygen/ http://www.coreboot.org/Developer_Manual
Did I miss anything?
Boris
--- On Tue, 4/19/11, Stefan Reinauer stefan.reinauer@coreboot.org wrote:
From: Stefan Reinauer stefan.reinauer@coreboot.org Subject: Re: [coreboot] Failed to launch windows 7 and two more questions ... To: "Boris Shpoungin" wmk587@yahoo.com Cc: coreboot@coreboot.org Date: Tuesday, April 19, 2011, 6:25 PM
- Boris Shpoungin wmk587@yahoo.com
[110419 23:31]:
Could you recommend any manual which describe coreboot
porting process to new not supported platform? Does it exist at all?
The Wiki is an excellent source of information.
Could you provide rough effort estimate to port
coreboot to new unsupported platform?
That incredibly depends on the porter's skill set. However, I have seen the following times to be accurate in some cases.
New mainboard: ~ 1 person month (assuming you want features like ACPI, S3, ...) This can vary a lot between 1 day and many weeks
New cpu / chipset: ~ 6 - 12 person months
These estimates obviously don't include the time you need to obtain the documentation for your chipset, which in some cases can take several months, too.
Stefan
-
Boris Shpoungin -
Peter Stuge -
Stefan Reinauer