see comment below
svn@openbios.org wrote:
Author: uwe Date: 2007-05-09 12:26:19 +0200 (Wed, 09 May 2007) New Revision: 317
Modified: LinuxBIOSv3/README Log: Short installation instructions for LinuxBIOSv3 (trivial).
Signed-off-by: Uwe Hermann uwe@hermann-uwe.de Acked-by: Uwe Hermann uwe@hermann-uwe.de
Modified: LinuxBIOSv3/README
--- LinuxBIOSv3/README 2007-05-06 18:52:16 UTC (rev 316) +++ LinuxBIOSv3/README 2007-05-09 10:26:19 UTC (rev 317) @@ -39,6 +39,38 @@
+Building and Installing +-----------------------
+Note: Currently only the x86 QEMU target is supported in LinuxBIOSv3.
+1) Build a payload:
- For example: FILO.
+2) Configure LinuxBIOS:
- $ make menuconfig
- Select at least the desired mainboard vendor, the mainboard device,
- the size of your ROM chip, and a payload.
+3) Build the LinuxBIOS ROM image:
- $ make
- The generated ROM image is build/linuxbios.rom.
Might want to add something around here about how to make qemu use the new rom.
+4) You can now test the LinuxBIOS image using:
- $ qemu -L build -hda /dev/zero -serial stdio
- If you have a full QEMU image with a Linux distribution installed,
- you can boot that Linux kernel by using a proper FILO payload and typing:
- $ qemu -L build -hda /tmp/qemu.img -serial stdio
Website and Mailing List
On Wed, May 09, 2007 at 11:35:38PM -0400, Corey Osgood wrote:
+3) Build the LinuxBIOS ROM image:
- $ make
- The generated ROM image is build/linuxbios.rom.
Might want to add something around here about how to make qemu use the new rom.
+4) You can now test the LinuxBIOS image using:
- $ qemu -L build -hda /dev/zero -serial stdio
It's right here: The '-L build/' tells QEMU to look in the build/ directory for its BIOS image file (which is called bios.bin, and is a copy of linuxbios.rom).
But yes, the documentation needs to be a bit more verbose.
Uwe.
Uwe Hermann wrote:
On Wed, May 09, 2007 at 11:35:38PM -0400, Corey Osgood wrote:
+3) Build the LinuxBIOS ROM image:
- $ make
- The generated ROM image is build/linuxbios.rom.
Might want to add something around here about how to make qemu use the new rom.
+4) You can now test the LinuxBIOS image using:
- $ qemu -L build -hda /dev/zero -serial stdio
It's right here: The '-L build/' tells QEMU to look in the build/ directory for its BIOS image file (which is called bios.bin, and is a copy of linuxbios.rom).
But yes, the documentation needs to be a bit more verbose.
Oh, whoops, my bad. I was thinking it had to be configured somewhere, but perhaps I'm thinking of BOCHS.
-Corey
On Thursday 10 May 2007 16:43, Corey Osgood wrote: [something about LinuxBIOSv3]
Is there a public repository for LinuxBIOSv3?
Juergen
* Juergen Beisert juergen127@kreuzholzen.de [070517 20:21]:
Is there a public repository for LinuxBIOSv3?
Yes, there is:
svn co svn://linuxbios.org/repository/LinuxBIOSv3
Best wishes, Stefan
--- Stefan Reinauer stepan@coresystems.de wrote:
- Juergen Beisert juergen127@kreuzholzen.de [070517 20:21]:
Is there a public repository for LinuxBIOSv3?
Yes, there is:
svn co svn://linuxbios.org/repository/LinuxBIOSv3
However, LinuxBIOSv3 doesn't show up in trac:
http://tracker.linuxbios.org/trac/LinuxBIOS/browser/trunk
Vlad
____________________________________________________________________________________Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC
* Vlad vladc6@yahoo.com [070517 22:05]:
--- Stefan Reinauer stepan@coresystems.de wrote:
- Juergen Beisert juergen127@kreuzholzen.de [070517 20:21]:
Is there a public repository for LinuxBIOSv3?
Yes, there is:
svn co svn://linuxbios.org/repository/LinuxBIOSv3
However, LinuxBIOSv3 doesn't show up in trac:
Yes. Trac can only handle a single repository. To start cleanly from the beginning, we chose to create a new repository instead.
Stefan
This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.