On Thu, Apr 11, 2024 at 10:51:35PM +0300, Daniil Tatianin wrote:
> Previously we would unconditionally lower the alignment for large BARs
> in case their alignment was greater than "pci_mem64_top >> 11", this
> would make it impossible to use these devices by the kernel:
> [ 13.821108] pci
On Tue, Apr 09, 2024 at 11:20:14AM -0400, Kevin O'Connor wrote:
> Introduce stdvga_dac_read_many() and stdvga_dac_write_many() for
> writing multiple dac palette entries. Convert the stdvga_dac_read()
> and stdvga_dac_write() low-level IO access functions in stdvgaio.c to
> access ju
On Sun, Apr 14, 2024 at 05:56:31PM +, Riku Viitanen wrote:
> > I think it would be preferable if mxm_setup() was passed the pci
> > device for uniformity, and have mxm_setup() call romfile_xxx() itself.
>
> Do you mean, run mxm30_setup unconditionally?
> And it checks if the file exists:
>
>
On Sun, Apr 14, 2024 at 05:39:21PM +, Riku Viitanen wrote:
> > Ah, I missed that vgahook_setup() checks for NULL. Out of curiosity,
> > is it possible to limit this support to a particular hardware vendor
> > instead of by existence of file?
>
> ATI, AMD, and Nvidia based MXM cards exist. I
On Sun, Apr 14, 2024 at 11:51:33AM -0400, Kevin O'Connor wrote:
> On Sun, Apr 14, 2024 at 10:30:55AM +, Riku Viitanen via SeaBIOS wrote:
> > VGAROMs on MXM graphics cards need certain int15h functions present
> > to function properly.
> >
> > On HP EliteBook 856
On Sun, Apr 14, 2024 at 10:30:55AM +, Riku Viitanen via SeaBIOS wrote:
> VGAROMs on MXM graphics cards need certain int15h functions present
> to function properly.
>
> On HP EliteBook 8560w with coreboot and Quadro 2000M, this warning
> is displayed for 30 seconds, making every boot
On Wed, Apr 10, 2024 at 02:24:50PM +0200, Gerd Hoffmann wrote:
> On Wed, Apr 10, 2024 at 11:01:34AM +0300, Daniil Tatianin wrote:
> > Previously we would unconditionally lower the alignment for large BARs
> > in case their alignment was greater than "pci_mem64_top >> 11", this
> > would make it
Introduce stdvga_dac_read_many() and stdvga_dac_write_many() for
writing multiple dac palette entries. Convert the stdvga_dac_read()
and stdvga_dac_write() low-level IO access functions in stdvgaio.c to
access just one color palette entry.
Signed-off-by: Kevin O'Connor
--
There should
On Tue, Apr 02, 2024 at 02:35:05PM -0400, Kevin O'Connor wrote:
> Add helper function and update the bochsvga.c code to use it. This
> emphasizes the relationship between stdvga_get_vertical_size() and
> stdvga_set_vertical_size() code.
>
> Signed-off-by: Kevin O'Connor
I commi
On Mon, Apr 01, 2024 at 11:51:22AM -0400, Kevin O'Connor wrote:
> This series adds comments to vgasrc/stdvga.c along with some variable
> and function renaming. The goal is to make it a little easier to
> understand this legacy code.
>
> There should be no functionality changes
On Thu, Apr 04, 2024 at 04:00:20PM +, Eduardo Batalha via SeaBIOS wrote:
> Hi,
>
> I had some old files saved in diskettes that I really needed to see, so I
> bought a floppy drive and installed it in my coreboot based computer, so, no,
> It's not a retro project. :)
>
> Regarding the
On Sat, Feb 10, 2024 at 11:17:54PM +0300, Michael Tokarev wrote:
> So.. the difference is vgabios only, not seabios (vgabios-stdvga in this
> case).
>
> And I can't get it to work with debugging vgabios, it always fails even with
> DEBUG_LEVEL=2
> (and level-1 logging isn't useful).
>
> I was
On Wed, Feb 07, 2024 at 03:21:15AM +0300, Michael Tokarev wrote:
> 07.02.2024 02:17, Michael Tokarev пишет:
[...]
> > The binary in question is vgabios-stdvga.bin.
[...]
>"SMBIOS 2.1 table length 66822 exceeds 65535"
>
> Which wont help with 7.2 machine types (it changes defaults for
On Fri, Aug 25, 2023 at 10:36:04PM +0100, Kieran Kunhya wrote:
> Hello,
>
> I'm trying to update this patch for 2017 as I have the same issue as the
> author in that I can't use the KVM virtual keyboard and a physical keyboard
> at the same time:
>
On Tue, May 30, 2023 at 03:44:05PM +0200, Niklas Cassel via SeaBIOS wrote:
> According to AHCI 1.3.1, 5.3.8.1 RegFIS:Entry, if ERR_STAT is set in the
> received FIS, the HBA shall jump to state ERR:FatalTaskfile, which will
> raise a TFES IRQ.
>
> This means that if ERR_STAT is set in the
On Fri, Jan 20, 2023 at 11:33:19AM +, David Woodhouse wrote:
> From: David Woodhouse
>
> When running under Xen, hvmloader places a table at 0x1000 with the e820
> information and BIOS tables. If this isn't present, SeaBIOS will
> currently panic.
>
> We now have support for running Xen
On Fri, Jan 20, 2023 at 11:33:19AM +, David Woodhouse wrote:
> From: David Woodhouse
>
> When running under Xen, hvmloader places a table at 0x1000 with the e820
> information and BIOS tables. If this isn't present, SeaBIOS will
> currently panic.
>
> We now have support for running Xen
On Wed, Jul 13, 2022 at 03:25:17AM +0200, Petr Cvek wrote:
> ASPI2DOS.SYS and KEYB.COM from Win 98 SE installation CD (and most likely
> other DOS versions too) depend on I/O port 0x61 bit 4 to be toggled. This
> requires timer 1 (I/O 0x41, legacy DRAM refresh) to be correctly set.
> Also Intel
On Wed, Jul 13, 2022 at 03:24:49AM +0200, Petr Cvek wrote:
> SeaBIOS can be used for booting legacy OS and also Linux is still using
> CMOS address 0x10 to configure floppy controller. Under these assumptions
> it makes sense to allow boot from CMOS defined floppy drives.
There was never really a
On Thu, Jul 07, 2022 at 12:06:16PM +0200, Gerd Hoffmann wrote:
> Bump default from 8 to 64 blocks. Using 8 by default leads
> to requests being splitted on qemu, which slows down boot.
>
> Some (temporary) debug logging added showed that almost all
> requests on a standard fedora install are
On Fri, May 20, 2022 at 03:19:03PM +, Lev Kujawski wrote:
> In accord with the El Torito specification[1], SeaBIOS now signals
> failure (AH=1 and CF) whenever attempts are made to terminate disk
> emulation (0x4B) for non-emulated drives. The prior behavior of always
> returning success
On Fri, May 20, 2022 at 03:19:01PM +, Lev Kujawski wrote:
> References:
> R. Brown, "INT 15 - OS HOOK - DEVICE POST (AT,PS)", in
> The x86 Interrupt List. https://www.cs.cmu.edu/~ralf/files.html
> [Updated: 2018-02-28].
>
> F. v. Gilluwe, The Undocumented PC. Boston, MA:
On Wed, Apr 27, 2022 at 09:22:02AM +0200, Gerd Hoffmann wrote:
> v4:
> - make calculations more robust.
>
> v3:
> - check size instead of end address.
The series looks good to me.
-Kevin
___
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe
On Wed, Apr 27, 2022 at 08:26:35AM +0200, Gerd Hoffmann wrote:
> > > if (!highram_start) {
> > > +if (e - s > BUILD_MAX_HIGHTABLE * 16)
> > > +highram_size = BUILD_MAX_HIGHTABLE;
> > > u32 newe = ALIGN_DOWN(e - highram_size, MALLOC_MIN_ALIGN);
> >
On Tue, Apr 26, 2022 at 10:56:42AM +0200, Gerd Hoffmann wrote:
> In case there is enough memory installed use a large ZoneHigh.
>
> Signed-off-by: Gerd Hoffmann
> ---
> src/config.h | 3 ++-
> src/malloc.c | 4 +++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
On Mon, Apr 25, 2022 at 09:41:45AM +0200, Gerd Hoffmann wrote:
> In case there is enough memory installed use a large ZoneHigh.
>
> Signed-off-by: Gerd Hoffmann
> ---
> src/config.h | 3 ++-
> src/malloc.c | 4 +++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
On Sun, Apr 24, 2022 at 07:29:56PM -0400, Keith Hui wrote:
> (Looping in the SeaBIOS mailing list again.)
>
> See this: https://www.seabios.org/Runtime_config
>
> It appears CMOS locations are a legacy artifact and files within the
> cbfs image (eg. etc/floppy0) is the preferred way of passing
On Fri, Apr 22, 2022 at 01:55:56PM +0200, Gerd Hoffmann wrote:
> Bump BUILD_MAX_HIGHTABLE from 256k to 1M to avoid running
> out of memory with very large smbios tables.
>
> Signed-off-by: Gerd Hoffmann
> ---
> src/config.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Thu, Apr 21, 2022 at 11:33:24AM +0200, Gerd Hoffmann wrote:
> When running out of memory get a chunk of memory from ZoneTmpHigh to
> expand ZoneHigh. Drop simliar logic fro pmm code because it's not
> needed ay more.
>
> This fixes some scalability problems, for example with lots of vcpus,
>
On Tue, Apr 19, 2022 at 11:46:59AM +0200, Gerd Hoffmann wrote:
> > > diff --git a/src/fw/mptable.c b/src/fw/mptable.c
> > > index 47385cc..3a7b02f 100644
> > > --- a/src/fw/mptable.c
> > > +++ b/src/fw/mptable.c
> >
> > If you look at the top of that file you'll see the notice:
> >
> > // DO NOT
On Fri, Apr 15, 2022 at 04:33:34PM +0530, Jay Khandkar wrote:
> Set the correct IOAPIC INTIN pin number for pci bus interrupt
> sources during MP spec table generation (on emulators). Currently,
> the pin number is set to the interrupt line field in the device's
> configuration space, which is set
On Sat, Apr 02, 2022 at 08:24:41PM +0200, Volker Rümelin wrote:
> This reset issue was reported on the QEMU issue tracker at
> https://gitlab.com/qemu-project/qemu/-/issues/766
>
> A reset with QEMU -machine q35 -accel tcg leads to a reset loop
> and with -machine q35 -accel kvm the reset only
On Sat, Mar 26, 2022 at 10:33:19AM +0100, Volker Rümelin wrote:
> After a reset of a QEMU -machine q35 guest, the PCI Express
> Enhanced Configuration Mechanism is disabled and the variable
> mmconfig no longer matches the configuration register PCIEXBAR
> of the Q35 chipset. Until the variable
On Tue, Mar 15, 2022 at 10:28:12AM +0300, Michael Tokarev wrote:
> 02.03.2022 05:19, Kevin O'Connor rote:
> > The 1.16.0 version of SeaBIOS has now been released. For more
> > information on the release, please see:
>
> Hi Kevin!
> This release seems to be missing at
smbios_build_tables() arguments optional
smbios: Make smbios_build_tables() ready for 64-bit tables
smbios: copy_smbios_30() function
smbios: Support SMBIOS 3.0 entry point at copy_table()
smbios: Support SMBIOS 3.0 entry point at smbios_romfile_setup()
Kevin O'Connor (13
I'm currently planning to make a release early next week. This will
be a v1.16.0 release.
If anyone knows of any critical bugs or deficiencies with the current
code, please let me know.
-Kevin
___
SeaBIOS mailing list -- seabios@seabios.org
To
On Sun, Jan 23, 2022 at 05:43:57PM +0100, Florian Larysch wrote:
> The LBA Format Data structure is dword-sized, but struct nvme_lba_format
> erroneously contains an additional member, misaligning all LBAF
> descriptors after the first and causing them to be misinterpreted.
> Remove it.
Thanks.
On Wed, Feb 02, 2022 at 11:50:50AM +0100, Alexander Graf wrote:
>
> On 02.02.22 02:52, Kevin O'Connor wrote:
> > On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
> > > On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
> > > > Thanks
On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
> On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
> > Thanks. I don't know enough about NVMe to review this patch though.
> > Maybe Julian or Alex could comment?
>
> Happy to hear their comment
On Fri, Jan 28, 2022 at 01:03:23PM +0100, Gerd Hoffmann wrote:
> On Thu, Jan 27, 2022 at 05:43:32PM +0100, Paul Menzel wrote:
> > Dear SeaBIOS folks,
> >
> >
> > with the latest NVMe fixes, would it make sense to tag a 1.15.1 release?
> >
> > The 1.16.0 release is planned for end of February,
On Sun, Jan 23, 2022 at 05:43:57PM +0100, Florian Larysch wrote:
> The LBA Format Data structure is dword-sized, but struct nvme_lba_format
> erroneously contains an additional member, misaligning all LBAF
> descriptors after the first and causing them to be misinterpreted.
> Remove it.
Thanks.
On Mon, Jan 24, 2022 at 10:20:53AM +0100, Jan Beulich via SeaBIOS wrote:
> Commit b68f313c9139 ("nvme: Record maximum allowed request size")
> introduced a use of "identify" past it being passed to free(). Latch the
> value of interest into a local variable.
>
> Reported-by: Coverity (ID 1497613)
On Fri, Jan 21, 2022 at 11:12:35AM -0500, Kevin O'Connor wrote:
> The variable rx_bytes is marked VARLOW, but there was a missing
> GET_LOW() to access rx_bytes. Fix by copying rx_bytes to a local
> variable and avoid the repetitive segment memory accesses.
>
> Reported-by: Gabe
On Fri, Jan 21, 2022 at 11:48:42AM -0500, Kevin O'Connor wrote:
> This is a resend of the previous series. Changes since last time:
>
> * Patch 1: Fix function comment on nvme_io_xfer()
> * Patch 3-5: Added "goto bounce" to nvme_io_xfer() as suggested by Alex
> * Patch
On Fri, Jan 21, 2022 at 09:44:46PM +0100, Alexander Graf wrote:
> On 21.01.22 17:54, Kevin O'Connor wrote:
> > On Fri, Jan 21, 2022 at 05:41:17PM +0100, Alexander Graf wrote:
> > > On 21.01.22 17:02, Kevin O'Connor wrote:
> > > > On Fri, Jan 21, 2022 at 03:28:33
On Fri, Jan 21, 2022 at 11:48:45AM -0500, Kevin O'Connor wrote:
> Rename nvme_build_prpl() to nvme_prpl_xfer() and directly invoke
> nvme_io_xfer() or nvme_bounce_xfer() from that function.
>
> Signed-off-by: Kevin O'Connor
> ---
> src/hw/nvme-int.h | 1 -
> s
On Fri, Jan 21, 2022 at 05:41:17PM +0100, Alexander Graf wrote:
> On 21.01.22 17:02, Kevin O'Connor wrote:
> > On Fri, Jan 21, 2022 at 03:28:33PM +0100, Alexander Graf wrote:
> > > On 19.01.22 19:45, Kevin O'Connor wrote:
> > > >if ((ns->block_si
There is no need to create multiple dma bounce buffers as the BIOS
disk code isn't reentrant capable.
Also, verify that the allocation succeeds.
Signed-off-by: Kevin O'Connor
Reviewed-by: Alexander Graf
---
src/hw/nvme-int.h | 3 ---
src/hw/nvme.c | 21 +++--
2 files
.
This patch builds the PRP maintenance data in the existing "dma bounce
buffer" and only builds it when needed.
Fixes: 01f2736cc905d ("nvme: Pass large I/O requests as PRP lists")
Reported-by: Matt DeVillier
Signed-off-by: Alexander Graf
Signed-off-by: Kevin O'Connor
---
src
When using a prp2 parameter, build it in nvme_prpl_xfer() and pass it
directly to nvme_io_xfer().
Signed-off-by: Kevin O'Connor
Reviewed-by: Alexander Graf
---
src/hw/nvme.c | 39 ++-
1 file changed, 18 insertions(+), 21 deletions(-)
diff --git a/src/hw
Rename nvme_build_prpl() to nvme_prpl_xfer() and directly invoke
nvme_io_xfer() or nvme_bounce_xfer() from that function.
Signed-off-by: Kevin O'Connor
---
src/hw/nvme-int.h | 1 -
src/hw/nvme.c | 46 --
2 files changed, 20 insertions(+), 27
Move bounce buffer processing to a new helper function.
Signed-off-by: Kevin O'Connor
Reviewed-by: Alexander Graf
---
src/hw/nvme.c | 35 +--
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/src/hw/nvme.c b/src/hw/nvme.c
index 608651a..d656e9b
Rename nvme_io_readwrite() to nvme_io_xfer() and change it so it
implements the debugging dprintf() and it returns -1 on an error.
Signed-off-by: Kevin O'Connor
Reviewed-by: Alexander Graf
---
src/hw/nvme.c | 37 ++---
1 file changed, 18 insertions(+), 19
checking for malloc failure
-Kevin
Kevin O'Connor (6):
nvme: Rework nvme_io_readwrite() to return -1 on error
nvme: Add nvme_bounce_xfer() helper function
nvme: Convert nvme_build_prpl() to nvme_prpl_xfer()
nvme: Pass prp1 and prp2 directly to nvme_io_xfer()
nvme: Build the page list
The variable rx_bytes is marked VARLOW, but there was a missing
GET_LOW() to access rx_bytes. Fix by copying rx_bytes to a local
variable and avoid the repetitive segment memory accesses.
Reported-by: Gabe Black
Signed-off-by: Volker Rümelin
Signed-off-by: Kevin O'Connor
---
src/sercon.c
On Thu, Jan 13, 2022 at 05:27:11PM +0100, Paul Menzel wrote:
> Dear Kevin,
>
>
> Am 13.01.22 um 17:19 schrieb Kevin O'Connor:
> > Add a hack to suppress spurious gcc array-bounds warning.
>
> Wow, thank you for fixing it. Maybe elaborate a little, what version it
>
On Fri, Jan 21, 2022 at 03:28:33PM +0100, Alexander Graf wrote:
>
> On 19.01.22 19:45, Kevin O'Connor wrote:
> > Commit 01f2736cc905d ("nvme: Pass large I/O requests as PRP lists")
> > introduced multi-page requests using the NVMe PRP mechanism. To store the
>
On Wed, Jan 19, 2022 at 10:08:49PM +0100, Volker Rümelin wrote:
> The variable rx_bytes is marked VARLOW. Add a missing GET_LOW()
> to access rx_bytes.
>
> Reported-by: Gabe Black
> Signed-off-by: Volker Rümelin
Thanks. Good catch!
I think we should fix this by copying the contents into a
There is no need to create multiple dma bounce buffers as the BIOS
disk code isn't reentrant capable.
Signed-off-by: Kevin O'Connor
---
This is a minor cleanup on top of the previous nvme code series.
-Kevin
---
src/hw/nvme-int.h | 3 ---
src/hw/nvme.c | 14 +-
2 files
.
This patch builds the PRP maintenance data in the existing "dma bounce
buffer" and only builds it when needed.
Fixes: 01f2736cc905d ("nvme: Pass large I/O requests as PRP lists")
Reported-by: Matt DeVillier
Signed-off-by: Alexander Graf
Signed-off-by: Kevin O'Connor
--
When using a prp2 parameter, build it in nvme_prpl_xfer() and pass it
directly to nvme_io_xfer().
Signed-off-by: Kevin O'Connor
---
src/hw/nvme.c | 39 ++-
1 file changed, 18 insertions(+), 21 deletions(-)
diff --git a/src/hw/nvme.c b/src/hw/nvme.c
index
Rename nvme_build_prpl() to nvme_prpl_xfer() and directly invoke
nvme_io_xfer() or nvme_bounce_xfer() from that function.
Signed-off-by: Kevin O'Connor
---
src/hw/nvme-int.h | 1 -
src/hw/nvme.c | 42 --
2 files changed, 16 insertions(+), 27
Move bounce buffer processing to a new helper function.
Signed-off-by: Kevin O'Connor
---
src/hw/nvme.c | 35 +--
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/src/hw/nvme.c b/src/hw/nvme.c
index a97501b..fd7c1d0 100644
--- a/src/hw/nvme.c
+++ b
Rename nvme_io_readwrite() to nvme_io_xfer() and change it so it
implements the debugging dprintf() and it returns -1 on an error.
Signed-off-by: Kevin O'Connor
---
src/hw/nvme.c | 34 +-
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/src/hw
us -snapshot -L test -chardev stdio,id=seabios -device
isa-debugcon,iobase=0x402,chardev=seabios -m 512 -drive
file=dos-drivec,if=none,id=drive0 -device nvme,drive=drive0,serial=nvme-1 -boot
menu=on
Thanks,
-Kevin
Kevin O'Connor (5):
nvme: Rework nvme_io_readwrite() to return -1 on error
nvme:
On Thu, Jan 13, 2022 at 11:56:35AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > 2. Commit the smbios 3 changes (and pcie-pci-bridge changes) and
> >release v1.15.0 in early January.
>
> I think all pending patches have been applied meanwhile.
> So time to enter 1.15 freeze and release in ~2
Add a hack to suppress spurious gcc array-bounds warning.
Signed-off-by: Kevin O'Connor
---
src/fw/smm.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/src/fw/smm.c b/src/fw/smm.c
index d90e43a..a0b50b2 100644
--- a/src/fw/smm.c
+++ b/src/fw/smm.c
On Sun, Dec 19, 2021 at 09:45:59AM -0500, Kevin O'Connor wrote:
> Signed-off-by: Kevin O'Connor
> ---
> scripts/readserial.py | 28 +++-
> 1 file changed, 11 insertions(+), 17 deletions(-)
>
FYI, I committed this series (along with the two gcc warni
It's simpler to use b"" designations around binary strings than to use
the as_bytes() function.
Signed-off-by: Kevin O'Connor
---
scripts/buildrom.py | 6 ++
scripts/checkrom.py | 4 +---
scripts/python23compat.py | 14 --
3 files changed, 3 inserti
Signed-off-by: Kevin O'Connor
---
scripts/readserial.py | 28 +++-
1 file changed, 11 insertions(+), 17 deletions(-)
diff --git a/scripts/readserial.py b/scripts/readserial.py
index a7383e8..e3f56e5 100755
--- a/scripts/readserial.py
+++ b/scripts/readserial.py
@@ -10,8
On Sat, Dec 18, 2021 at 09:13:57PM +0100, Paul Menzel wrote:
> Dear Kevin,
>
>
> Am 18.12.21 um 19:10 schrieb Kevin O'Connor:
> > Use a different definition for the linker script symbol to avoid a gcc
> > warning.
>
> What GCC version did you use, and which
Use a different definition for the linker script symbol to avoid a gcc
warning.
Signed-off-by: Kevin O'Connor
---
src/memmap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/memmap.h b/src/memmap.h
index 22bd4bc..32ca265 100644
--- a/src/memmap.h
+++ b/src/memmap.h
Some versions of gcc complain when VAR16 is used in both the header
and C files - use only in the C file to fix the warning.
Signed-off-by: Kevin O'Connor
---
vgasrc/svgamodes.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/vgasrc/svgamodes.h b/vgasrc/svgamodes.h
index
On Thu, Dec 16, 2021 at 08:20:58AM +0100, Gerd Hoffmann wrote:
> Add all three 4k modes. Computer monitors typically use
> the first one (3840x2160).
>
> Add 16 and 32 bpp variants. 24bpp is dead these days, and
> software which is so old that still uses those modes most
> likely doesn't even
On Tue, Dec 07, 2021 at 09:31:05AM +0800, Andy Pei wrote:
> if driver reads data larger than VIRTIO_BLK_F_SIZE_MAX, it will cause
> some issue to the DMA engine.
> So add VIRTIO_BLK_F_SIZE_MAX feature support, when upper software
> wants to read data larger than VIRTIO_BLK_F_SIZE_MAX, virtio-blk
>
On Mon, Nov 29, 2021 at 06:48:10AM -0500, Igor Mammedov wrote:
> Since QEMU-6.1, Q35 machine is using ACPI PCI hotplug by default.
> However SeaBIOS did not take in account pcie-pci-bridge and treated it
> as any other PCIe device which is not correct in the case of the bridge.
>
> Patch [1/2]
On Thu, Dec 10, 2020 at 04:26:21PM -0500, Eduardo Habkost wrote:
> This series implements support for SMBIOS 3.0 entry points in
>
> SeaBIOS.
>
> The main advantage of SMBIOS 3.0 entry points is the higher limit
> for total table size. The SMBIOS 2.1 64435 bytes limit can be
> easily hit in
On Fri, Dec 03, 2021 at 09:35:24AM +0100, Paul Menzel wrote:
> Dear Kevin,
>
>
> Am 03.12.21 um 03:40 schrieb Kevin O'Connor:
> > The 1.15.0 version of SeaBIOS has now been released. For more
> > information on the release, please see:
>
> Thank you for cu
On Wed, Dec 01, 2021 at 12:21:34PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > I'm not sure what you'd prefer to do with the SeaBIOS release though.
> > We have a couple of high-level options:
> >
> > 1. Release v1.15.0 this week without these changes (tag 64f37cc5).
> >
> > 2. Commit the smbios
vme: Clean up nvme_cmd_readwrite()
Kevin O'Connor (1):
docs: Note v1.15.0 release
Matt DeVillier (1):
usb.c: Fix devices using non-primary interface descriptor
Mike Banon (1):
Support booting USB drives with a write protect switch enabled
Sergei Trofimovich (1):
vgas
On Tue, Nov 23, 2021 at 09:50:44AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > Damn. Support for smbiod 3.0 fall completely through the cracks:
> > >
> > > https://www.mail-archive.com/seabios@seabios.org/msg12438.html
> > >
> > > The qemu-side changes have long been merged (except for
On Mon, Nov 29, 2021 at 06:48:10AM -0500, Igor Mammedov wrote:
> Since QEMU-6.1, Q35 machine is using ACPI PCI hotplug by default.
> However SeaBIOS did not take in account pcie-pci-bridge and treated it
> as any other PCIe device which is not correct in the case of the bridge.
Thanks. It looks
On Mon, Nov 22, 2021 at 10:15:49AM +0100, Gerd Hoffmann wrote:
> On Thu, Oct 21, 2021 at 09:43:39PM -0400, Kevin O'Connor wrote:
> > On Thu, Oct 21, 2021 at 03:01:23PM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > It's been a while since
On Thu, Oct 21, 2021 at 03:01:23PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> It's been a while since the last release, we have some nice but
> unreleased bits in the master branch (tpm and nvme improvements
> for example), time for a new release I think.
>
> How about freeze in a week, release by
On Tue, Oct 19, 2021 at 07:50:40PM -0400, Brad Smith via SeaBIOS wrote:
> On 8/14/2021 1:02 AM, Brad Smith wrote:
>
> > As an OpenBSD developer I'm very interested in these patches. SeaBIOS is
> > the only package
> > left in our ports tree still using lld to link and one of very few ports
> >
On Tue, Sep 07, 2021 at 05:05:52PM -0400, Stefan Berger wrote:
> In the rare case of a TPM 2 failure, disable the platform hierarchy after
> disabling the endorsement and owner hierarchies.
Thanks. I committed this change.
-Kevin
___
SeaBIOS mailing
On Sat, Jun 26, 2021 at 10:13:40PM +, Alex Martens via SeaBIOS wrote:
> Signed-off-by: Alex Martens
Thanks. I committed this change.
-Kevin
___
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-le...@seabios.org
On Wed, Jun 09, 2021 at 01:31:59PM -0400, Stefan Berger wrote:
> Fix two details of the logs:
>
> - Set the field 'SpecErrata' to 2 as required by specs.
> - Write the separator into the log entry's event field.
>
> Signed-off-by: Stefan Berger
Thanks. I committed this change.
-Kevin
On Mon, Jun 14, 2021 at 01:35:47PM -0400, Stefan Berger wrote:
> This PR adds the implementations for sha{256, 384, 512} and makes use
> of the hash implementation when extending the PCRs of the respective
> banks rather than always using the sha1 and zero-padding it for the PCR
> banks of a TPM
On Mon, Jun 14, 2021 at 01:35:47PM -0400, Stefan Berger wrote:
> This PR adds the implementations for sha{256, 384, 512} and makes use
> of the hash implementation when extending the PCRs of the respective
> banks rather than always using the sha1 and zero-padding it for the PCR
> banks of a TPM
On Fri, Jun 04, 2021 at 07:59:27PM +0200, Volker Rümelin wrote:
> 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
>
On Fri, Jun 04, 2021 at 07:59:27PM +0200, Volker Rümelin wrote:
> 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
>
On Wed, Jun 02, 2021 at 09:25:54PM +0200, Volker Rümelin wrote:
> > On Tue, Jun 01, 2021 at 09:06:54PM +0200, Volker Rümelin wrote:
> > > The variables data, func, thread and cur are input operands for
> > > the asm statement in run_thread(). The assembly code clobbers
> > > these inputs.
> > >
>
On Tue, Jun 01, 2021 at 09:06:54PM +0200, Volker Rümelin wrote:
> The variables data, func, thread and cur are input operands for
> the asm statement in run_thread(). The assembly code clobbers
> these inputs.
>
> From the gcc documentation chapter Extended-Asm, Input Operands:
> "It is not
On Mon, May 31, 2021 at 07:55:28AM +0200, Gerd Hoffmann wrote:
> 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.
On Thu, May 27, 2021 at 03:43:51PM -0300, Heitor Alves de Siqueira wrote:
> On Thu, May 27, 2021 at 11:44 AM Kevin O'Connor wrote:
> >
> > The purpose of this code is to restore the NMI_DISABLE_BIT to what it
> > was prior to call32_prep(). If something c
On Thu, May 27, 2021 at 10:52:27AM +0200, Gerd Hoffmann wrote:
> 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.
On Thu, May 27, 2021 at 09:25:01AM -0300, Heitor Alves de Siqueira wrote:
> We should disable NMIs when accessing CMOS ports during state restore,
> like it's done during state backup in call32_prep().
>
> Signed-off-by: Heitor Alves de Siqueira
> ---
> src/stacks.c | 2 +-
> 1 file changed, 1
On Wed, May 26, 2021 at 09:49:55AM +0200, Gerd Hoffmann wrote:
> Gerd Hoffmann (2):
>
> nvme: improve namespace allocation
>
> nvme: drive desc should not include the newline
>
Thanks. It looks fine to me.
-Kevin
___
SeaBIOS mailing list --
On Thu, May 20, 2021 at 11:18:48PM +0100, Sergei Trofimovich wrote:
> From: Sergei Trofimovich
>
> 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
1 - 100 of 2786 matches
Mail list logo
