All, I have been working with LinuxBIOS on my Geode for several weeks now. I would first like to say, "I love it!". If does what it is intended to do very well. The only drawback I see is documentation. After watching the mailing lists for these past few weeks, I believe that most issues could be solved with some updated and decent docs. As a LinuxBIOS newbie, myself, I found trying to determine the correct option flags nearly impossible. It would be great to at least have something that described what each option did. For example, BOOT_IDE, BOOT_TFTP, USE_ELF_BOOT, USE_GENERIC_ROM, and others could be grouped together to decribe where LinuxBIOS gets the kernel image.
I would be willing to help get the docs inorder, but as a relative newbie to LinuxBIOS, I probably know only a handful of options anyway. Any Thoughts? John
I too feel that it would be good, if we have good documentation for the LInuxBIOS code. Atleast for the generic code like startup and bootstrap codes...
I too fighting with the linuxbios code for past one month, I feel that we can have group of people (who ever interested) and the start documentation for the code and the problem they faced while bring up the Linuxbios. It would be realy helpful for newbie.
As my contribution, I will start the documentation on the intial part of the Linuxbios code (i.e., Bootstrap code and the Ram initialization) Though the RAM initialization is not common for all the motherboard, I will try to list out the points need to taken care for RAM initialization.
Thanks Siva On Thu, 2003-01-02 at 18:37, John Allen wrote:
All, I have been working with LinuxBIOS on my Geode for several weeks now. I would first like to say, "I love it!". If does what it is intended to do very well. The only drawback I see is documentation. After watching the mailing lists for these past few weeks, I believe that most issues could be solved with some updated and decent docs. As a LinuxBIOS newbie, myself, I found trying to determine the correct option flags nearly impossible. It would be great to at least have something that described what each option did. For example, BOOT_IDE, BOOT_TFTP, USE_ELF_BOOT, USE_GENERIC_ROM, and others could be grouped together to decribe where LinuxBIOS gets the kernel image.
I would be willing to help get the docs inorder, but as a relative newbie to LinuxBIOS, I probably know only a handful of options anyway. Any Thoughts? John
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On 2 Jan 2003, sivakumar wrote:
I too feel that it would be good, if we have good documentation for the LInuxBIOS code. Atleast for the generic code like startup and bootstrap codes...
the first question I have is; have you tried make documentation
in your build directory?
In the end I would like to have this produce a little manual for a given mainboard. There is lots of documentaiton missing for this, however.
ron
Yes, I agree that using doxygen for documentation is good idea. But we need to add enough description of the code in source code so that doxygen will come up with good documentation.
- Siva
On Thu, 2003-01-02 at 22:39, Ronald G. Minnich wrote:
On 2 Jan 2003, sivakumar wrote:
I too feel that it would be good, if we have good documentation for the LInuxBIOS code. Atleast for the generic code like startup and bootstrap codes...
the first question I have is; have you tried make documentation
in your build directory?
In the end I would like to have this produce a little manual for a given mainboard. There is lots of documentaiton missing for this, however.
ron
On 3 Jan 2003, sivakumar wrote:
Yes, I agree that using doxygen for documentation is good idea. But we need to add enough description of the code in source code so that doxygen will come up with good documentation.
agree. Anything you write will be a huge help.
ron
we need docs.
For a start, we need updated howto's for motherboards, but more important we need a "generic HOWTO" for new motherboards.
I'm not even sure where to start, I've tried a few times but it is hard.
ron