On Mon, 2012-02-20 at 09:22 +0000, Roger Pau Monné wrote:
> Hello,
>
> When compiling SeaBIOS with busybox and uclibc 0.9.33, I've hit the
> following error:
>
> Build Kconfig config file
> Compiling whole program out/ccode.16.s
> Compiling to assembler out/asm-offsets.s
> Generating offset file out/asm-offsets.h
> gen-offsets.sh: applet not found
I guess this means your shell comes from busybox?
> When looking into gen-offsets.sh [0] I've realized there's a strange
> shebang in the script ":", is this normal? Replacing ":" with
> "#!/bin/sh" solves the problem, but I don't understand why the ":"
> shebang works for some (on Debian stable it works ok) and what it
> means.
I've no idea either -- I've copied the seabios ML.
Ian.
>
> Thanks, Roger.
>
> [0] http://code.coreboot.org/p/seabios/source/tree/rel-1.6.3.1/tools/gen-offset…
Hi all,
I am trying my luck with coreboot and seabios to get VGA working on an LX800
platform. At the moment I am not sure what options I need to enable in coreboot
and seabios to enable VGA.
Coreboot does its jobs and starts SeaBIOS, but VGA seems not to work.
thanks for every hint
--
Christian Gmeiner, MSc
Run vgabios during resume from S3 by default on QEMU. QEMU
still able to modify SeaBIOS behavior if it wishes so by providing
etc/s3-resume-vga-init file. With QEMU emulated vga cards this behaviour
is desirable otherwise console becomes unusable with Linux guests after
resume. Since we control vgabios source we can be sure that running it
on resume from S3 is safe.
Signed-off-by: Gleb Natapov <gleb(a)redhat.com>
---
Older versions of SeaBIOS had a runtime configure option (disabled by
default) to enable this behaviour and RHEL always enabled it, so this
code path is well tested. But QEMU upstream always compiled SeaBIOS
with default options and hence this patch will modify upstream
behaviour. Are there any objections to this change from QEMU side?
diff --git a/src/optionroms.c b/src/optionroms.c
index 27cfffd..06db1c1 100644
--- a/src/optionroms.c
+++ b/src/optionroms.c
@@ -423,7 +423,7 @@ vga_setup(void)
// Load some config settings that impact VGA.
EnforceChecksum = romfile_loadint("etc/optionroms-checksum", 1);
- S3ResumeVgaInit = romfile_loadint("etc/s3-resume-vga-init", 0);
+ S3ResumeVgaInit = romfile_loadint("etc/s3-resume-vga-init", !CONFIG_COREBOOT);
ScreenAndDebug = romfile_loadint("etc/screen-and-debug", 1);
if (CONFIG_OPTIONROMS_DEPLOYED) {
--
Gleb.
Commit 1e749c85 removed the definition of process_usb_op(); let's remove
the declaration too.
The same commit added process_scsi_op(). The function has no declaration
that is also not a definition, and its only call site is in the same file
as the definition. Give the function internal linkage.
Build tested.
Signed-off-by: Laszlo Ersek <lersek(a)redhat.com>
---
Please keep me CC'd, I'm not subscribed. Thanks.
src/block.c | 2 +-
src/usb-msc.h | 1 -
2 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/src/block.c b/src/block.c
index eeebd83..ccf4ee6 100644
--- a/src/block.c
+++ b/src/block.c
@@ -276,7 +276,7 @@ map_floppy_drive(struct drive_s *drive_g)
* 16bit calling interface
****************************************************************/
-int
+static int
process_scsi_op(struct disk_op_s *op)
{
if (!CONFIG_USB_MSC)
diff --git a/src/usb-msc.h b/src/usb-msc.h
index a8686a3..12d749c 100644
--- a/src/usb-msc.h
+++ b/src/usb-msc.h
@@ -8,7 +8,6 @@ struct usb_interface_descriptor;
struct usb_pipe;
int usb_msc_init(struct usb_pipe *pipe
, struct usb_interface_descriptor *iface, int imax);
-int process_usb_op(struct disk_op_s *op);
/****************************************************************
--
1.7.1
On Fri, Feb 17, 2012 at 03:42:20PM -0700, Steve Goodrich wrote:
> I'm trying to debug SeaBIOS (built into coreboot) with GDB. Would someone
> point me to information on how I would generate debug symbols for SeaBIOS?
The out/rom.o file has debugging symbols for the 32bit code. The
out/rom16.o has the 16bit code debugging symbols.
-Kevin
On Fri, Feb 17, 2012 at 03:59:04PM -0700, Steve Goodrich wrote:
> One other question if you're able to help: Where can I find documentation on
> the syntax of entries in the bootorder file? I need to add them for my
> platform, but I'm a bit confused as to how they're constructed. I'm
> googling, but I've not found a description of the syntax.
There is a description at:
http://www.coreboot.org/SeaBIOS#Configuring_boot_order
-Kevin
I'm stuck with a few questions about applying SeaBIOS to Bochs
(Windows), hoping someone is willing to give out some helpful hints.
1) Can the downloadable v1.6.3 binary directly be used in Bochs, or is a
recompile needed? Thought I read some docs about MTRR config options.
2) What minimal system requirements does SeaBIOS put on a virtual
machine? 80586, 2MB, PCI ? 80386, 1MB, ISA ?
3) Is there an opensource BIOS, usable in Bochs and QEMU, that does work
with only 1MB RAM assigned to the VM? SeaBIOS fails this.
As much as I like VMware, and QEMU (including SeaBIOS) as well,
evaluation of all the 22 criteria for my goal (see [1]) resulted
selecting Bochs as least bad emulation/virtualisation/simulation
solution. Hopefully QEMU can match these criteria someday.
with best regards,
Bernd Blaauw
[1] : [ http://sourceforge.net/mailarchive/message.php?msg_id=28786659 ]