Category: coreboot

after several times long discussion with marc. We finally decide to make the filo kconfig as below rules:

1) move filo source code to coreboot/payloads. We should put all of there payloads under this directory right?

2) check the filo libpayload configuration before loading kconfig. The design of the payload infrastructure is gonna to make libpayload be included, but the only method for that is use the makefile “source” command, so we should tell this “source ” where this libpayload is. if the filo located in coreboot/payloads/, then for filo the payload must be under the path “../libpayload”.

3) merge the libpayload configuration into filo payload configuration, after loading libpayload kconfig under the filo kconfig, after this configuration all of the configuration are saved in the default .config file. Then copy the whole .config into libpayload directory. these configuration about filo may be useless for libpayload, but it does not matter, which will not influent the libpayload installation.

4) the next step may be check if there is any conflict between the libpayload and the other paylaods.

I would like to say the first public mainboard porting has already successfully  been done. The whole work also including fintek f71863fg superio supporting. I would like to see the linux login shell shows on the screen. The vgabios is still working under the coreboot and payload process. But it always caused blank or flashing some nonsense character. I really did not know why. the VGA is extracted from the AMI bios. the strange things in that original vbios has an different device id  with (1002,9611). it is (1002,9610). As is known, 0x960 is the 780 vbios (HD3200), but Jetway PA78VM5 has an 780v(HD3100)vbios. I changed the vbios’s device id to make coreboot can load it correctly. it worked, but seems did not work very fine.

the other ongoing progress is digging the coreboot fam10 problems. the latest coreboot can not run very well with most of 780 family mainboard which including mahogany. So i should dig into the code to check out the which revision caused it.

In the next week, i will begin my next mainboard porting which is got from L84Supper. Thanks to him for sending me the board. After i know that shinner coreboot code can not be released, i should trying much more public mainboard porting.

after a long time learning and code checking, several things has been done:

1)kconfig language have already been learned,  i learned all of these things from “http://www.kernel.org/doc/Documentation/kbuild/kconfig-language.txt”

2)much clear with libpayload xcompile code and menuconfig things. i reviewed all of the code under libpayload/util.

question is i do not know what interface should be added into the libpayload menuconfig. and i also have an doubt about the coreboot xcompile. why not just put the files into the trunk but instead of making the downloaded with and script?