SeaBIOS October 2016

seabios@seabios.org

10 participants
16 discussions

[PATCH] docs: fix various typos and inconsistency
by Piotr Król 19 Oct '16

19 Oct '16

Signed-off-by: Piotr Król <piotr.krol(a)3mdeb.com> --- docs/Debugging.md | 4 ++-- docs/Execution_and_code_flow.md | 10 +++++----- docs/Runtime_config.md | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/Debugging.md b/docs/Debugging.md index 7ab5d02d8cad..13cee4dce592 100644 --- a/docs/Debugging.md +++ b/docs/Debugging.md @@ -60,7 +60,7 @@ mkfifo qemudebugpipe qemu -chardev pipe,path=qemudebugpipe,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios ... ``` -and then in another session: +And then in another session: `/path/to/seabios/scripts/readserial.py -nf qemudebugpipe` @@ -77,7 +77,7 @@ Debugging with gdb on QEMU ========================== One can use gdb with QEMU to debug system images. To do this, add '-s --S' to the qemu command line. For example: +-S' to the QEMU command line. For example: `qemu -bios out/bios.bin -fda myfdimage.img -s -S` diff --git a/docs/Execution_and_code_flow.md b/docs/Execution_and_code_flow.md index a54776eef140..4a7ba8d9e4ad 100644 --- a/docs/Execution_and_code_flow.md +++ b/docs/Execution_and_code_flow.md @@ -30,7 +30,7 @@ called in 32bit mode. This then calls post.c:handle_post(). On CSM, the build arranges for romlayout.S:entry_csm() to be called (in 16bit mode). This then calls csm.c:handle_csm() in 32bit mode. Unlike on the emulators and coreboot, the SeaBIOS CSM POST phase is -orchastrated with UEFI and there are several calls back and forth +orchestrated with UEFI and there are several calls back and forth between SeaBIOS and UEFI via handle_csm() throughout the POST process. @@ -58,7 +58,7 @@ transition to 32bit mode and call boot.c:handle_19() or boot.c:handle_18(). The boot phase is technically also part of the "runtime" phase of -SeaBIOS. It is typically invoked immiediately after the POST phase, +SeaBIOS. It is typically invoked immediately after the POST phase, but it can also be invoked by an operating system or be invoked multiple times in an attempt to find a valid boot media. Although the boot phase C code runs in 32bit mode it does not have write access to @@ -120,7 +120,7 @@ atomic memory accesses and complex locking is not required. The goal of these threads is to reduce overall boot time by parallelizing hardware delays. (For example, by allowing the wait for -an ATA harddrive to spinup and respond to commands to occur in +an ATA hard drive to spin-up and respond to commands to occur in parallel with the wait for a PS/2 keyboard to respond to a setup command.) These hardware setup threads are only available during the "setup" sub-phase of the [POST phase](#POST_phase). @@ -144,7 +144,7 @@ interrupts disabled. The first reason is that external software may override the default SeaBIOS handlers that are called on a hardware interrupt event. Indeed, it is common for DOS based applications to do this. These legacy third party interrupt handlers may have -undocumented expections (such as stack location and stack size) and +undocumented expectations (such as stack location and stack size) and may attempt to call back into the various SeaBIOS software services. Greater compatibility and more reproducible results can be achieved by only permitting hardware interrupts at specific points (via yield() @@ -171,7 +171,7 @@ memory"](Memory Model). It ensures SeaBIOS uses a minimal amount of a callers stack (typically no more than 16 bytes) for these legacy calls. (More recently defined BIOS interfaces such as those that support 16bit protected and 32bit protected mode calls standardize a -minimum stack size with adequete space, and SeaBIOS generally will not +minimum stack size with adequate space, and SeaBIOS generally will not use its extra stack in these cases.) The code to implement this stack "hopping" is in romlayout.S and in diff --git a/docs/Runtime_config.md b/docs/Runtime_config.md index 517129621e15..a2617481a6be 100644 --- a/docs/Runtime_config.md +++ b/docs/Runtime_config.md @@ -157,7 +157,7 @@ into bootorder. For example, the file: /pci@i0cf8/*@f/drive@1/disk@0 ``` -will instruct SeaBIOS to attempt to boot from the given USB drive +Will instruct SeaBIOS to attempt to boot from the given USB drive first and then attempt the given ATA harddrive second. SeaBIOS also supports a special "HALT" directive. If a line that -- 2.9.3

2 4

Re: [SeaBIOS] [PATCH] vgabios: Reorder video modes to work around a Windows bug
by Ladi Prosek 19 Oct '16

19 Oct '16

On Wed, Oct 19, 2016 at 10:06 AM, Ladi Prosek <lprosek(a)redhat.com> wrote: > On Wed, Oct 19, 2016 at 1:29 AM, Kevin O'Connor <kevin(a)koconnor.net> wrote: >> On Mon, Oct 17, 2016 at 05:53:04PM +0200, Ladi Prosek wrote: >>> Windows Server 2016 and Windows 10 RS1 come with a bug in its blue screen >>> of death rendering logic which prevents it from generating crash dumps. >>> >>> The bug does not manifest if Windows sees a suitable 32 bpp video mode >>> before a suitable 24 bpp video mode in the list of modes returned from >>> vgabios. This commit moves all 32 bpp modes to the front of the list to >>> make sure that this is always the case. >>> >>> Signed-off-by: Ladi Prosek <lprosek(a)redhat.com> >>> --- >>> vgasrc/bochsvga.c | 39 ++++++++++++++++++++------------------- >>> 1 file changed, 20 insertions(+), 19 deletions(-) >>> >>> diff --git a/vgasrc/bochsvga.c b/vgasrc/bochsvga.c >>> index ec5d101..c5d1511 100644 >>> --- a/vgasrc/bochsvga.c >>> +++ b/vgasrc/bochsvga.c >>> @@ -28,6 +28,25 @@ static struct bochsvga_mode >>> u16 mode; >>> struct vgamode_s info; >>> } bochsvga_modes[] VAR16 = { >>> + /* 32 bpp BOCHS modes */ >>> + { 0x140, { MM_DIRECT, 320, 200, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x141, { MM_DIRECT, 640, 400, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x142, { MM_DIRECT, 640, 480, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x143, { MM_DIRECT, 800, 600, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x144, { MM_DIRECT, 1024, 768, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x145, { MM_DIRECT, 1280, 1024, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x147, { MM_DIRECT, 1600, 1200, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x14c, { MM_DIRECT, 1152, 864, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x177, { MM_DIRECT, 1280, 768, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x17a, { MM_DIRECT, 1280, 800, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x17d, { MM_DIRECT, 1280, 960, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x180, { MM_DIRECT, 1440, 900, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x183, { MM_DIRECT, 1400, 1050, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x186, { MM_DIRECT, 1680, 1050, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x189, { MM_DIRECT, 1920, 1200, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x18c, { MM_DIRECT, 2560, 1600, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x18f, { MM_DIRECT, 1280, 720, 32, 8, 16, SEG_GRAPH } }, >>> + { 0x192, { MM_DIRECT, 1920, 1080, 32, 8, 16, SEG_GRAPH } }, >>> /* standard modes */ >>> { 0x100, { MM_PACKED, 640, 400, 8, 8, 16, SEG_GRAPH } }, >>> { 0x101, { MM_PACKED, 640, 480, 8, 8, 16, SEG_GRAPH } }, >>> @@ -56,50 +75,32 @@ static struct bochsvga_mode >>> { 0x11D, { MM_DIRECT, 1600, 1200, 15, 8, 16, SEG_GRAPH } }, >>> { 0x11E, { MM_DIRECT, 1600, 1200, 16, 8, 16, SEG_GRAPH } }, >>> { 0x11F, { MM_DIRECT, 1600, 1200, 24, 8, 16, SEG_GRAPH } }, >>> - /* BOCHS modes */ >>> - { 0x140, { MM_DIRECT, 320, 200, 32, 8, 16, SEG_GRAPH } }, >>> - { 0x141, { MM_DIRECT, 640, 400, 32, 8, 16, SEG_GRAPH } }, >>> - { 0x142, { MM_DIRECT, 640, 480, 32, 8, 16, SEG_GRAPH } }, >>> - { 0x143, { MM_DIRECT, 800, 600, 32, 8, 16, SEG_GRAPH } }, >>> - { 0x144, { MM_DIRECT, 1024, 768, 32, 8, 16, SEG_GRAPH } }, >>> - { 0x145, { MM_DIRECT, 1280, 1024, 32, 8, 16, SEG_GRAPH } }, >>> + /* 8, 15, 16, and 24 bpp BOCHS modes */ >>> { 0x146, { MM_PACKED, 320, 200, 8, 8, 16, SEG_GRAPH } }, >>> - { 0x147, { MM_DIRECT, 1600, 1200, 32, 8, 16, SEG_GRAPH } }, >> >> Thanks. Instead of moving all of the 32bit modes to the top of the >> list, can the 32bit modes be kept next to the other modes with the >> same resolution, just above the 24bpp mode? > > Yes, that would work too. As long as 32 bpp come before 24 bpp for the > same resolution, it will be fine. > >> Also, all of the mode numbers above 0x11b are arbitrary, so it would >> be preferable to renumber the mode numbers as lines are moved. > > Will do. > >> We were about to make a SeaBIOS release - does this need to go into >> that release? > > It would be highly desired as the problematic Windows builds have > already RTM'ed. > > I'll send a v2 with the changes as suggested above. Actually, I spoke too soon. The problematic 24 bpp mode that Windows picks right now is 118 and that's within the standard range so I can't move 144 above it and renumber. What would be considered safer, keeping the same mode numbers or partially renumbering to keep them monotonically increasing except for the standard range? > Thanks! > Ladi

1 0

[PATCH] vgabios: Reorder video modes to work around a Windows bug
by Ladi Prosek 19 Oct '16

19 Oct '16

Windows Server 2016 and Windows 10 RS1 come with a bug in its blue screen of death rendering logic which prevents it from generating crash dumps. The bug does not manifest if Windows sees a suitable 32 bpp video mode before a suitable 24 bpp video mode in the list of modes returned from vgabios. This commit moves all 32 bpp modes to the front of the list to make sure that this is always the case. Signed-off-by: Ladi Prosek <lprosek(a)redhat.com> --- vgasrc/bochsvga.c | 39 ++++++++++++++++++++------------------- 1 file changed, 20 insertions(+), 19 deletions(-) diff --git a/vgasrc/bochsvga.c b/vgasrc/bochsvga.c index ec5d101..c5d1511 100644 --- a/vgasrc/bochsvga.c +++ b/vgasrc/bochsvga.c @@ -28,6 +28,25 @@ static struct bochsvga_mode u16 mode; struct vgamode_s info; } bochsvga_modes[] VAR16 = { + /* 32 bpp BOCHS modes */ + { 0x140, { MM_DIRECT, 320, 200, 32, 8, 16, SEG_GRAPH } }, + { 0x141, { MM_DIRECT, 640, 400, 32, 8, 16, SEG_GRAPH } }, + { 0x142, { MM_DIRECT, 640, 480, 32, 8, 16, SEG_GRAPH } }, + { 0x143, { MM_DIRECT, 800, 600, 32, 8, 16, SEG_GRAPH } }, + { 0x144, { MM_DIRECT, 1024, 768, 32, 8, 16, SEG_GRAPH } }, + { 0x145, { MM_DIRECT, 1280, 1024, 32, 8, 16, SEG_GRAPH } }, + { 0x147, { MM_DIRECT, 1600, 1200, 32, 8, 16, SEG_GRAPH } }, + { 0x14c, { MM_DIRECT, 1152, 864, 32, 8, 16, SEG_GRAPH } }, + { 0x177, { MM_DIRECT, 1280, 768, 32, 8, 16, SEG_GRAPH } }, + { 0x17a, { MM_DIRECT, 1280, 800, 32, 8, 16, SEG_GRAPH } }, + { 0x17d, { MM_DIRECT, 1280, 960, 32, 8, 16, SEG_GRAPH } }, + { 0x180, { MM_DIRECT, 1440, 900, 32, 8, 16, SEG_GRAPH } }, + { 0x183, { MM_DIRECT, 1400, 1050, 32, 8, 16, SEG_GRAPH } }, + { 0x186, { MM_DIRECT, 1680, 1050, 32, 8, 16, SEG_GRAPH } }, + { 0x189, { MM_DIRECT, 1920, 1200, 32, 8, 16, SEG_GRAPH } }, + { 0x18c, { MM_DIRECT, 2560, 1600, 32, 8, 16, SEG_GRAPH } }, + { 0x18f, { MM_DIRECT, 1280, 720, 32, 8, 16, SEG_GRAPH } }, + { 0x192, { MM_DIRECT, 1920, 1080, 32, 8, 16, SEG_GRAPH } }, /* standard modes */ { 0x100, { MM_PACKED, 640, 400, 8, 8, 16, SEG_GRAPH } }, { 0x101, { MM_PACKED, 640, 480, 8, 8, 16, SEG_GRAPH } }, @@ -56,50 +75,32 @@ static struct bochsvga_mode { 0x11D, { MM_DIRECT, 1600, 1200, 15, 8, 16, SEG_GRAPH } }, { 0x11E, { MM_DIRECT, 1600, 1200, 16, 8, 16, SEG_GRAPH } }, { 0x11F, { MM_DIRECT, 1600, 1200, 24, 8, 16, SEG_GRAPH } }, - /* BOCHS modes */ - { 0x140, { MM_DIRECT, 320, 200, 32, 8, 16, SEG_GRAPH } }, - { 0x141, { MM_DIRECT, 640, 400, 32, 8, 16, SEG_GRAPH } }, - { 0x142, { MM_DIRECT, 640, 480, 32, 8, 16, SEG_GRAPH } }, - { 0x143, { MM_DIRECT, 800, 600, 32, 8, 16, SEG_GRAPH } }, - { 0x144, { MM_DIRECT, 1024, 768, 32, 8, 16, SEG_GRAPH } }, - { 0x145, { MM_DIRECT, 1280, 1024, 32, 8, 16, SEG_GRAPH } }, + /* 8, 15, 16, and 24 bpp BOCHS modes */ { 0x146, { MM_PACKED, 320, 200, 8, 8, 16, SEG_GRAPH } }, - { 0x147, { MM_DIRECT, 1600, 1200, 32, 8, 16, SEG_GRAPH } }, { 0x148, { MM_PACKED, 1152, 864, 8, 8, 16, SEG_GRAPH } }, { 0x149, { MM_DIRECT, 1152, 864, 15, 8, 16, SEG_GRAPH } }, { 0x14a, { MM_DIRECT, 1152, 864, 16, 8, 16, SEG_GRAPH } }, { 0x14b, { MM_DIRECT, 1152, 864, 24, 8, 16, SEG_GRAPH } }, - { 0x14c, { MM_DIRECT, 1152, 864, 32, 8, 16, SEG_GRAPH } }, { 0x175, { MM_DIRECT, 1280, 768, 16, 8, 16, SEG_GRAPH } }, { 0x176, { MM_DIRECT, 1280, 768, 24, 8, 16, SEG_GRAPH } }, - { 0x177, { MM_DIRECT, 1280, 768, 32, 8, 16, SEG_GRAPH } }, { 0x178, { MM_DIRECT, 1280, 800, 16, 8, 16, SEG_GRAPH } }, { 0x179, { MM_DIRECT, 1280, 800, 24, 8, 16, SEG_GRAPH } }, - { 0x17a, { MM_DIRECT, 1280, 800, 32, 8, 16, SEG_GRAPH } }, { 0x17b, { MM_DIRECT, 1280, 960, 16, 8, 16, SEG_GRAPH } }, { 0x17c, { MM_DIRECT, 1280, 960, 24, 8, 16, SEG_GRAPH } }, - { 0x17d, { MM_DIRECT, 1280, 960, 32, 8, 16, SEG_GRAPH } }, { 0x17e, { MM_DIRECT, 1440, 900, 16, 8, 16, SEG_GRAPH } }, { 0x17f, { MM_DIRECT, 1440, 900, 24, 8, 16, SEG_GRAPH } }, - { 0x180, { MM_DIRECT, 1440, 900, 32, 8, 16, SEG_GRAPH } }, { 0x181, { MM_DIRECT, 1400, 1050, 16, 8, 16, SEG_GRAPH } }, { 0x182, { MM_DIRECT, 1400, 1050, 24, 8, 16, SEG_GRAPH } }, - { 0x183, { MM_DIRECT, 1400, 1050, 32, 8, 16, SEG_GRAPH } }, { 0x184, { MM_DIRECT, 1680, 1050, 16, 8, 16, SEG_GRAPH } }, { 0x185, { MM_DIRECT, 1680, 1050, 24, 8, 16, SEG_GRAPH } }, - { 0x186, { MM_DIRECT, 1680, 1050, 32, 8, 16, SEG_GRAPH } }, { 0x187, { MM_DIRECT, 1920, 1200, 16, 8, 16, SEG_GRAPH } }, { 0x188, { MM_DIRECT, 1920, 1200, 24, 8, 16, SEG_GRAPH } }, - { 0x189, { MM_DIRECT, 1920, 1200, 32, 8, 16, SEG_GRAPH } }, { 0x18a, { MM_DIRECT, 2560, 1600, 16, 8, 16, SEG_GRAPH } }, { 0x18b, { MM_DIRECT, 2560, 1600, 24, 8, 16, SEG_GRAPH } }, - { 0x18c, { MM_DIRECT, 2560, 1600, 32, 8, 16, SEG_GRAPH } }, { 0x18d, { MM_DIRECT, 1280, 720, 16, 8, 16, SEG_GRAPH } }, { 0x18e, { MM_DIRECT, 1280, 720, 24, 8, 16, SEG_GRAPH } }, - { 0x18f, { MM_DIRECT, 1280, 720, 32, 8, 16, SEG_GRAPH } }, { 0x190, { MM_DIRECT, 1920, 1080, 16, 8, 16, SEG_GRAPH } }, { 0x191, { MM_DIRECT, 1920, 1080, 24, 8, 16, SEG_GRAPH } }, - { 0x192, { MM_DIRECT, 1920, 1080, 32, 8, 16, SEG_GRAPH } }, }; static int dispi_found VAR16 = 0; -- 2.5.5

2 2

[PATCH 0/7] serial console support
by Gerd Hoffmann 19 Oct '16

19 Oct '16

Hi, After a looong break finally the next round of the seabios serial console patches. cheers, Gerd Gerd Hoffmann (7): std: add cp437 to unicode map kbd: make enqueue_key public, add ascii_to_keycode paravirt: read QEMU_CFG_NOGRAPHIC, store in etc/sercon-enable romfile add serial console support sercon: split-output implementation sercon: add compile time option [hack] ignore sgabios, enable sercon instead Makefile | 3 +- src/Kconfig | 5 + src/clock.c | 1 + src/cp437.c | 275 +++++++++++++++++++++++ src/cp437.h | 1 + src/fw/paravirt.c | 2 + src/kbd.c | 18 +- src/misc.c | 2 + src/optionroms.c | 17 +- src/romlayout.S | 14 ++ src/sercon.c | 660 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ src/util.h | 5 + 12 files changed, 999 insertions(+), 4 deletions(-) create mode 100644 src/cp437.c create mode 100644 src/cp437.h create mode 100644 src/sercon.c -- 1.8.3.1

2 8

[PATCH 0/5] serial console support
by Gerd Hoffmann 13 Oct '16

13 Oct '16

Hi, Next round of serial console patches, Still not ready to merge. Headline feature of this version is split mode (i.e. output on both vga and serial). Have a initial working implementation now, logic is simliar to the vgabios timer hook (as suggested by Kevin). Also changed the output logic, down to a one-cell buffer (char+attr) for output. Cursor updates are simply written to BDA now, with the actual move being done lazily when printing the next character or checking for keyboard input. That is especially useful for splitmode as we can simply skip the cursor position updates and let the vgabios do them instead. TODO list: * compile time (CONFIG_*) option. * input handling cleanups. * implement missing int10h functions. * more testing. cheers, Gerd Gerd Hoffmann (5): std: add cp437 to unicode map kbd: make enqueue_key public, add ascii_to_keycode paravirt: read QEMU_CFG_NOGRAPHIC, store in etc/sercon-enable romfile add serial console support [wip] sercon: initial split-output implementation Makefile | 7 +- src/clock.c | 1 + src/fw/paravirt.c | 2 + src/kbd.c | 17 +- src/misc.c | 2 + src/optionroms.c | 9 +- src/romlayout.S | 39 ++++ src/sercon.c | 621 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ src/std/cp437.c | 275 ++++++++++++++++++++++++ src/std/cp437.h | 1 + src/util.h | 5 + 11 files changed, 974 insertions(+), 5 deletions(-) create mode 100644 src/sercon.c create mode 100644 src/std/cp437.c create mode 100644 src/std/cp437.h -- 1.8.3.1

3 16

next release?
by Paolo Bonzini 12 Oct '16

12 Oct '16

Hi, is there a plan for SeaBIOS 1.10? It would be nice for one to have the mpt-scsi driver included in the next QEMU release. :) Thanks, Paolo

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS October 2016