SeaBIOS

seabios@seabios.org

3775 discussions

[PATCH 1/1] usb-hid: Increase MAX_KBD_EVENT
by seabios＠desire.ch 08 Mar '21

08 Mar '21

From: Stefan Ott <stefan(a)ott.net> Some USB keyboards use max packet sizes beyond the current maximum supported by SeaBIOS. This increases the available size to support these keyboards. Signed-off-by: Stefan Ott <stefan(a)ott.net> --- src/hw/usb-hid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/hw/usb-hid.c b/src/hw/usb-hid.c index a22765b..92c6b19 100644 --- a/src/hw/usb-hid.c +++ b/src/hw/usb-hid.c @@ -56,7 +56,7 @@ struct keyevent { u8 keys[6]; }; -#define MAX_KBD_EVENT 10 +#define MAX_KBD_EVENT 16 static int usb_kbd_setup(struct usbdevice_s *usbdev -- 2.30.1

4 3

Re: How to boot from DVD/CD automatically, instead of pressing a key by hand?
by 舛讹 03 Mar '21

03 Mar '21

Gerd Hoffmann wrote: > On Sun, Feb 28, 2021 at 02:22:53PM -0000, Yiguang Chen wrote: > >   Most time, When a vm with seabios start. The bios will > > display such info: > >  ----- > >  Seabios (version rel-1.13-0 ......) > >  Machine UUID ... > >   > >  IPXE .. > >   > >  IPXE.. > >   > >  Booting from DVD/CD... > >  Press any key to boot from CD or DVD. > >  --- > >   > >  It means that have a bootable cdrom to boot. But If we want to boot > >  from cdrom, we must press any key as what the warning had said. If it > >  is possible to boot from DVD/CD automatically, instead of pressing a > >  key by hand?  > This is a windows install iso, right? You are right. The cdrom is a windows install iso.  > This isn't seabios, the windows boot loader does that.  I think windows > does this only in case it finds a bootable hard disk.  So when booting > the guest with a fresh & blank virtual hard disk it should boot the > windows installer without asking for a key press. It seems that the windows install iso cause this behavior and the seabios source code prove this. --- roms/seabios/src/boot.c static void boot_cdrom(struct drive_s *drive) {     if (! CONFIG_CDROM_BOOT)         return;     printf("Booting from DVD/CD...\n");     int status = cdrom_boot(drive);     if (status) {         printf("Boot failed: Could not read from CDROM (code %04x)\n", status);         return;     }     u8 bootdrv = CDEmu.emulated_drive;     u16 bootseg = CDEmu.load_segment;     tpm_add_cdrom(bootdrv, MAKE_FLATPTR(bootseg, 0), 512);     /* Canonicalize bootseg:bootip */     u16 bootip = (bootseg & 0x0fff) << 4;     bootseg &= 0xf000;     call_boot_entry(SEGOFF(bootseg, bootip), bootdrv); } --- Best regards, YiguangChen

1 0

Re: How to boot from DVD/CD automatically, instead of pressing a key by hand?
by Valentine 02 Mar '21

02 Mar '21

Oh, sorry, previous replies fell to spam folder and I forgot to check it. :)

1 0

Re: How to boot from DVD/CD automatically, instead of pressing a key by hand?
by Valentine 02 Mar '21

02 Mar '21

Hello, Yiguang! If I'm not mistaken, 1st "Booting from DVD/CD..." is generated by SeaBIOS: https://github.com/coreboot/seabios/blob/58a44be024f69d2e4d2b58553529230abd… But 2nd "Press any key to boot from CD or DVD..." is shown by loader from CD. If other CDs boot without waiting for keypress, it's not SeaBIOS. That is, you'll need to tune the loader on CD itself to remove the message. Best regards, Valentine.

1 0

How to boot from DVD/CD automatically, instead of pressing a key by hand?
by Yiguang Chen 01 Mar '21

01 Mar '21

Most time, When a vm with seabios start. The bios will display such info: ----- Seabios (version rel-1.13-0 ......) Machine UUID ... IPXE .. IPXE.. Booting from DVD/CD... Press any key to boot from CD or DVD. --- It means that have a bootable cdrom to boot. But If we want to boot from cdrom, we must press any key as what the warning had said. If it is possible to boot from DVD/CD automatically, instead of pressing a key by hand? Looking forward to your feedback, YiguangChen

4 3

Re: [PATCH 28/31] string.c: reimplement mem*_far() functions for PA-RISC
by Valentine 16 Feb '21

16 Feb '21

Hello, Helge! I meant, to use: #ifdef CONFIG_PA_RISC // PA-RISC code #else // x86 code #endif Then if CONFIG_PA_RISC is not defined, the compilation will go as before without the need of toolchain modification. But, of course, you're right, the difference is not that big. Best regards, Valentine.

2 1

Re: [PATCH 28/31] string.c: reimplement mem*_far() functions for PA-RISC
by Valentine 13 Feb '21

13 Feb '21

> +#if CONFIG_X86 I understand that Helge adapted sources for PA-RISC, but will not it be more convenient to use#if CONFIG_PA_RISC So that by default SeaBIOS would compile as usual? Best regards,Valentine ---From: Helge DellerDate: 12.02.2021 1:08 (GMT+03:00)Subject: [SeaBIOS] [PATCH 28/31] string.c: reimplement mem*_far() functions for PA-RISC

2 1

[PATCH 20/31] output.c: Add PA-RISC specific output behaviour
by Helge Deller 11 Feb '21

11 Feb '21

On PA-RISC call an own screenc() implementation which doesn't use int10, prevent the Intel-specific \r newline when printing \n and don't output to serial debug port. Signed-off-by: Helge Deller <deller(a)gmx.de> --- src/output.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/src/output.c b/src/output.c index 0184444..6141fb6 100644 --- a/src/output.c +++ b/src/output.c @@ -18,6 +18,9 @@ #include "stacks.h" // call16_int #include "string.h" // memset #include "util.h" // ScreenAndDebug +#if CONFIG_PARISC +#include "parisc/sticore.h" +#endif struct putcinfo { void (*func)(struct putcinfo *info, char c); @@ -44,7 +47,8 @@ debug_putc(struct putcinfo *action, char c) qemu_debug_putc(c); if (!MODESEGMENT) coreboot_debug_putc(c); - serial_debug_putc(c); + if (!CONFIG_PARISC) + serial_debug_putc(c); } // Flush any pending output to debug port(s). @@ -74,6 +78,7 @@ static struct putcinfo debuginfo = { debug_putc }; static void screenc(char c) { +#if CONFIG_X86 if (!MODESEGMENT && GET_IVT(0x10).segoff == FUNC16(entry_10).segoff) // No need to thunk to 16bit mode if vgabios is not present return; @@ -84,6 +89,9 @@ screenc(char c) br.al = c; br.bl = 0x07; call16_int(0x10, &br); +#else + parisc_screenc(c); +#endif } // Handle a character from a printf request. @@ -92,7 +100,7 @@ screen_putc(struct putcinfo *action, char c) { if (ScreenAndDebug) debug_putc(&debuginfo, c); - if (c == '\n') + if (CONFIG_X86 && c == '\n') screenc('\r'); screenc(c); } -- 2.29.2

1 11

PCIe (x4) M.2 slot does not see NVME disks at SeaBIOS boot menu.
by dponamorev＠gmail.com 10 Feb '21

10 Feb '21

Hi! Custom motherboard on Intel Atom C3338 with PCIe (x4) M.2 slot does not see NVME disks at SeaBIOS boot menu. (SeaBIOS (version rel-1.13.0-1-g3ab38b1)) Does not load the operating system from these drives. If you boot from another media, then the NVME disk is seen in the system and works fine. In the logs there is a warning at "void *pci_enable_membar" function in the "coreboot/payloads/external/SeaBIOS/seabios/src/hw/pcidevice.c" file line 186. Warning message: WARNING - internal error detected at pci_enable_membar:186! // Verify a memory bar and return it to the caller void * pci_enable_membar(struct pci_device *pci, u32 addr) { wait_preempt(); u32 bar = pci_config_readl(pci->bdf, addr); if (bar & PCI_BASE_ADDRESS_SPACE_IO) { warn_internalerror(); return NULL; } if (bar & PCI_BASE_ADDRESS_MEM_TYPE_64) { u32 high = pci_config_readl(pci->bdf, addr+4); if (high) { dprintf(1, "Can not map memory bar over 4Gig\n"); return NULL; } } bar &= PCI_BASE_ADDRESS_MEM_MASK; if (bar + 4*1024*1024 < 20*1024*1024) { // Bar doesn't look valid (it is in last 4M or first 16M) warn_internalerror(); =========================================>WARNING! return NULL; } pci_config_maskw(pci->bdf, PCI_COMMAND, 0, PCI_COMMAND_MEMORY); pci->have_driver = 1; return (void*)bar; } Some values: for Samsung NVME disk 0x144d:0xa804; bdf: 0x200 bar: 0x4 at (u32 bar = pci_config_readl(pci->bdf, addr)) bar: 0x0 at (bar &= PCI_BASE_ADDRESS_MEM_MASK) have_driver = 0. If you boot from another media, then the NVME disk is seen in the system and works fine. lspci: 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 fdisk: Disk /dev/nvme0n1: 232,9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x5107186e Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT /dev/nvme0n1p2 1126400 488394751 487268352 232,4G 7 HPFS/NTFS/exFAT Tried with different NVME drives with different controllers. What could be the reason? Driver needed? Best regards, Dmitry Ponamorev

2 1

Possibility to merge the SeaBIOS-parisc tree?
by Helge Deller 09 Feb '21

09 Feb '21

Dear SeaBIOS developers, a few years back I forked the SeaBIOS sources to create a SeaBIOS firmware for usage with the parisc/hppa architecture. This fork is on github: https://github.com/hdeller/seabios-hppa Main goal of this fork was to provide a firmware which can be used to boot a virtual parisc machine with qemu. This firmware reuses most of the SeaBIOS/x86 drivers and infrastructure and works quite well today. Now I would prefer to merge back my changes into the official seabios git tree, if people here agree. Of course there are some patches which touches the generic code, e.g. parisc doesn't need segments and uses 32bit addresses for I/O and serial ports, which I've addressed with generic #ifdefs and typedefs, e.g.: #if CONFIG_X86 typedef u16 portaddr_t; #else typedef unsigned int portaddr_t; #endif I think all code can be merged back in a way that it neither affects runtime behaviour, build environment or code generation of x86, which I understand is the most important goal. My main question is now: Do you agree that it's worth and useful to merge the code back in? If so, how should I proceed? Send in first initial patches which could be applied, step by step? Generally I'd prefer if I could work privately with one or two seabios core developers to speed it up too... Just as a *reference*, I've created two patches which show the changes. Those will be then split it up into small logical parts before committing into the SeaBIOS tree: This patch touches only the generic existing seabios code: http://backup.parisc-linux.org/qemu/seabios-short-patch.txt Same patch as above, but including all new files I added to the new "src/parisc" directory: http://backup.parisc-linux.org/qemu/seabios-full-patch.txt Looking forward to your feedback, Helge

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS