SeaBIOS

seabios@seabios.org

8 participants
3775 discussions

INT 14H
by Paul Edwards 28 Jun '21

28 Jun '21

Hi. INT 14H is designed to read/write to a serial port. I would like my software (OS) that uses this interface to, on a machine that doesn't have a serial port, be directed to some other device, like bluetooth to my phone or Wifi to my router. Is this possible? Thanks. Paul.

2 1

[PATCH v4 0/2] fix PS/2 keyboard initialization failures
by Volker Rümelin 09 Jun '21

09 Jun '21

Hi, I wrote a few patches for qemu [1] and patch 10/11 exposes a bug in seabios. Sometimes the PS/2 keyboard initialization fails and seabios doesn't detect the keyboard. This patch fixes the PS/2 keyboard initialization. I wouldn't be surprised if my patch also fixes PS/2 keyboard initialization problems on bare metal. A few bug reports look very similar to what I see on my computer with qemu. With best regards, Volker v2: Kevin suggested to call check_irqs() in run_thread(). v3: Add a new patch to fix the asm constraints in run_thread(). The changes are required for the next patch. Kevin suggested to call check_irqs() after the new thread ran in run_thread(). Fixed an error in the commit message. Call check_irqs() after switch_next() in yield(). v4: Drop the patch to fix the asm constraints in run_thread(). Rename cur to edx in the asm constraints in run_thread() to make it clear that edx is clobbered after the asm statement. Volker Rümelin (2): stacks: call check_irqs() in run_thread() stacks: call check_irqs() after switch_next() src/stacks.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) -- 2.26.2

2 4

[PATCH v3 0/3] fix PS/2 keyboard initialization failures
by Volker Rümelin 04 Jun '21

04 Jun '21

Hi, I wrote a few patches for qemu [1] and patch 10/11 exposes a bug in seabios. Sometimes the PS/2 keyboard initialization fails and seabios doesn't detect the keyboard. This patch fixes the PS/2 keyboard initialization. I wouldn't be surprised if my patch also fixes PS/2 keyboard initialization problems on bare metal. A few bug reports look very similar to what I see on my computer with qemu. With best regards, Volker v2: Kevin suggested to call check_irqs() in run_thread(). v3: Add a new patch to fix the asm constraints in run_thread(). The changes are required for the next patch. Kevin suggested to call check_irqs() after the new thread ran in run_thread(). Fixed an error in the commit message. Call check_irqs() after switch_next() in yield(). [1]https://lists.nongnu.org/archive/html/qemu-devel/2021-05/msg02152.html Volker Rümelin (3): stacks: fix asm constraints in run_thread() stacks: call check_irqs() in run_thread() stacks: call check_irqs() after switch_next() src/stacks.c | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) -- 2.26.2

2 7

[PATCH v3] Increate BUILD_MIN_BIOSTABLE for large roms
by Gerd Hoffmann 04 Jun '21

04 Jun '21

BUILD_MIN_BIOSTABLE reserves space in the f-segment. Some data structures -- for example disk drives known to seabios -- must be stored there, so the space available here limits the number of devices seabios is able to manage. This patch sets BUILD_MIN_BIOSTABLE to 8k for bios images being 256k or larger in size. 32bit code is moved off in that case, so we have more room in the f-segment then. Signed-off-by: Gerd Hoffmann <kraxel(a)redhat.com> --- scripts/layoutrom.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/scripts/layoutrom.py b/scripts/layoutrom.py index 6616721d1b58..abebf0211fa9 100755 --- a/scripts/layoutrom.py +++ b/scripts/layoutrom.py @@ -651,6 +651,10 @@ def main(): # Read kconfig config file config = scanconfig(cfgfile) + # larger roms have more room in the f-segment due to moving out 32bit code + if config.get('CONFIG_ROM_SIZE') >= 256: + BUILD_MIN_BIOSTABLE = 8192 + # Figure out which sections to keep. allsections = info16[0] + info32seg[0] + info32flat[0] symbols = {'16': info16[1], '32seg': info32seg[1], '32flat': info32flat[1]} -- 2.31.1

3 4

[PATCH 0/1] stacks: disable NMIs during state restore on call32_post()
by Heitor Alves de Siqueira 01 Jun '21

01 Jun '21

Hi all, We've had reports of users hitting KVM emulation failures in certain workloads and were able to track down a missing NMI_DISABLE_BIT in call32_post() when accessing CMOS ports. This patch disables NMIs on state restore, following other accesses to CMOS_PORT_INDEX throughout the seabios code. Heitor Alves de Siqueira (1): stacks: fix missing NMI_DISABLE_BIT on call32_post() src/stacks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.31.1

2 5

[PATCH 0/2] nvme fixes
by Gerd Hoffmann 01 Jun '21

01 Jun '21

Gerd Hoffmann (2): nvme: improve namespace allocation nvme: drive desc should not include the newline src/hw/nvme-int.h | 1 - src/hw/nvme.c | 44 ++++++++++++++++++-------------------------- 2 files changed, 18 insertions(+), 27 deletions(-) -- 2.31.1

3 4

[PATCH v2] make BUILD_MIN_BIOSTABLE configurable
by Gerd Hoffmann 27 May '21

27 May '21

BUILD_MIN_BIOSTABLE reserves space in the f-segment. Some data structures -- for example disk drives known to seabios -- must be stored there, so the space available here limits the number of devices seabios is able to manage. This patch adds an config option for BUILD_MIN_BIOSTABLE so the size of the reservation can be configured at build time. Default is 8k for bios images being 256k or larger in size (32bit code is moved off then so we have more room in the f-segment), 2k (current value) otherwise. Signed-off-by: Gerd Hoffmann <kraxel(a)redhat.com> --- Makefile | 2 +- scripts/layoutrom.py | 3 ++- src/Kconfig | 7 +++++++ 3 files changed, 10 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 3d8943ef5f25..ddcd1dff399d 100644 --- a/Makefile +++ b/Makefile @@ -172,7 +172,7 @@ $(OUT)romlayout16.lds: $(OUT)ccode32flat.o $(OUT)code32seg.o $(OUT)ccode16.o $(O $(Q)$(OBJDUMP) -thr $(OUT)code32flat.o > $(OUT)code32flat.o.objdump $(Q)$(OBJDUMP) -thr $(OUT)code32seg.o > $(OUT)code32seg.o.objdump $(Q)$(OBJDUMP) -thr $(OUT)code16.o > $(OUT)code16.o.objdump - $(Q)$(PYTHON) ./scripts/layoutrom.py $(OUT)code16.o.objdump $(OUT)code32seg.o.objdump $(OUT)code32flat.o.objdump $(OUT)$(KCONFIG_AUTOHEADER) $(OUT)romlayout16.lds $(OUT)romlayout32seg.lds $(OUT)romlayout32flat.lds + $(Q)$(PYTHON) ./scripts/layoutrom.py $(OUT)code16.o.objdump $(OUT)code32seg.o.objdump $(OUT)code32flat.o.objdump $(OUT)$(KCONFIG_AUTOHEADER) $(OUT)romlayout16.lds $(OUT)romlayout32seg.lds $(OUT)romlayout32flat.lds $(CONFIG_MIN_BIOSTABLE) # These are actually built by scripts/layoutrom.py above, but by pulling them # into an extra rule we prevent make -j from spawning layoutrom.py 4 times. diff --git a/scripts/layoutrom.py b/scripts/layoutrom.py index 6616721d1b58..94deca9fcc85 100755 --- a/scripts/layoutrom.py +++ b/scripts/layoutrom.py @@ -636,7 +636,8 @@ def scanconfig(file): def main(): # Get output name - in16, in32seg, in32flat, cfgfile, out16, out32seg, out32flat = sys.argv[1:] + in16, in32seg, in32flat, cfgfile, out16, out32seg, out32flat, biostable = sys.argv[1:] + BUILD_MIN_BIOSTABLE = biostable * 1024 # Read in the objdump information infile16 = open(in16, 'r') diff --git a/src/Kconfig b/src/Kconfig index 3a8ffa15fded..95519fc50fa3 100644 --- a/src/Kconfig +++ b/src/Kconfig @@ -140,6 +140,13 @@ endchoice it into 128 KB (which was big enouth for a long time) you'll probably have to disable some featues such as xhci support. + config MIN_BIOSTABLE + int "biostable size (in KB)" + default 8 if ROM_SIZE >= 256 + default 2 + help + Memory space for BIOS tables in f-segment. + endmenu menu "Hardware support" -- 2.31.1

2 1

[PATCH v2 0/1] fix PS/2 keyboard initialization failures
by Volker Rümelin 26 May '21

26 May '21

2 3

[PATCH] vgasrc/vgalayout.lds.S: ignore .node.gnu.property (binutils-2.36 support)
by Sergei Trofimovich 26 May '21

26 May '21

From: Sergei Trofimovich <slyfox(a)gentoo.org> Modern binutils unconditionally tracks x86_64 ISA levels in intermediate files in .note.gnu.property. Custom liker script does not handle the section and complains about it: ld --gc-sections -T out/vgasrc/vgalayout.lds out/vgaccode16.o \ out/vgaentry.o out/vgaversion.o -o out/vgarom.o ld: section .note.gnu.property LMA [0000000000000000,0000000000000027] \ overlaps section .text LMA [0000000000000000,00000000000098af] The change ignores .note.gnu.property section. Signed-off-by: Sergei Trofimovich <slyfox(a)gentoo.org> --- vgasrc/vgalayout.lds.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vgasrc/vgalayout.lds.S b/vgasrc/vgalayout.lds.S index 533734d..e17d89e 100644 --- a/vgasrc/vgalayout.lds.S +++ b/vgasrc/vgalayout.lds.S @@ -19,5 +19,5 @@ SECTIONS // Discard regular data sections to force a link error if // 16bit code attempts to access data not marked with VAR16. - /DISCARD/ : { *(.text*) *(.rodata*) *(.data*) *(.bss*) *(COMMON) } + /DISCARD/ : { *(.text*) *(.rodata*) *(.data*) *(.bss*) *(COMMON) *(.note.gnu.property) } } -- 2.31.1

2 4

SeaBIOS fails to boot from NVMe controller with lots of namespaces
by Thanos Makatos 26 May '21

26 May '21

I'm using SeaBIOS (b0d61ec) to boot from a virtual NVMe controller that has relatively many namespaces (64). The exact error is : /3ff9f000\ Start thread |3ff9f000| Searching bootorder for: /pci@i0cf8/*@6 ... |3ff9f000| WARNING - Unable to allocate resource at nvme_controller_enable:632! I changed the number of namespaces my controller reports to 1 and it worked fine. Is there an easy way to get around this or do I have to fix the code? I haven't looked at the code in detail, but I think we don't have to allocate the array of namespaces in nvme_controller_enable; instead, we can probe a namespace right before we attempt to boot from it (not sure where exactly this is done).

4 16

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS