I have given up on appending VGA ROM with coreboot image. Instead I use the serial port for all the debug messages and then Geode LX frame buffer driver takes over immediately after loading the kernel.
-Phani
On Mon, Mar 17, 2008 at 7:34 PM, Phani Babu Giddi phanig@gmail.com wrote:
Yes currently I am using the serial port and it works well.
Thanks for the clarification on the blob address. I am still wondering why I am coreboot is not able to see the VSA. The only other suspicsion I have is with the VGA ROM thats because the size was 32K and atleast for some other boards I read that it should be 36K and the last 4K of the VGA ROM cannot be retrived using "dd".
I tried searching for tools to decompress and extract the VGA ROM but the links seem to be broken...
-Phani
On Mon, Mar 17, 2008 at 5:31 PM, Peter Stuge peter@stuge.se wrote:
On Mon, Mar 17, 2008 at 01:48:42PM -0800, Phani Babu Giddi wrote:
But I wanted to see some of the debug messages that are given out at the time of initializing core boot.
I would recommend using the serial port for this.
Just one question I was using a 512k part and then I switched over to a 1MB flash part and the VSA initialization went through without trouble, so where do you think is the blob location hardcoded.
--8<-- src/cpu/amd/model_lx/vsmsetup.c, do_vsmbios() rom = ((unsigned long)0) - (ROM_SIZE + 36 * 1024); -->8--
As Marc confirmed it's hardcoded to the beginning of the defined rom size, but not hardcoded to an address. Sorry for the confusion.
//Peter
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot