From: Kevin O'Connor <kevin@koconnor.net>
To: seabios@seabios.org, qemu-devel@nongnu.org, coreboot@coreboot.org
Subject: [ANNOUNCE] SeaBIOS 1.16.0
Date: Tue, 1 Mar 2022 21:19:06 -0500 [thread overview]
Message-ID: <Yh7UGn7Km6CJM2MG@morn> (raw)
The 1.16.0 version of SeaBIOS has now been released. For more
information on the release, please see:
https://seabios.org/Releases
New in this release:
* SMBIOS v3.0 support on QEMU
* Several bug fixes and code cleanups.
For information on obtaining SeaBIOS, please see:
https://seabios.org/Download
===== git shortlog -n rel-1.15.0..rel-1.16.0 =====
Eduardo Habkost (19):
biostables: copy_fseg_table() function
util.h: Delete unused get_smbios_entry_point() prototype
smbios: Rename code specific for SMBIOS 2.1 entry points
smbios: Generic smbios_next() function
smbios: smbios_get_tables() function
smbios: Use smbios_get_tables()/smbios_next() at display_uuid()
smbios: smbios_major_version()/smbios_minor_version() helpers
tpm: Use smbios_get_tables()
csm: Don't check SMBios21Addr before calling copy_smbios_21()
smbios: Make SMBios21Addr variable static
smbios: Use smbios_next() at smbios_romfile_setup()
smbios: Extract SMBIOS table building code to separate function
smbios: Make smbios_build_tables() more generic
smbios: smbios_21_setup_entry_point() function
smbios: Make some 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):
vgasrc: Don't use VAR16 in header files to fix gcc warning
memmap: Fix gcc out-of-bounds warning
readserial: Improve Python3 compatibility
scripts: Remove python23compat.py
smm: Suppress gcc array-bounds warnings
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 in the existing dma buffer
nvme: Only allocate one dma bounce buffer for all nvme drives
sercon: Fix missing GET_LOW() to access rx_bytes
docs: Note v1.16.0 release
Andy Pei (3):
virtio-blk: add feature VIRTIO_BLK_F_SIZE_MAX and VIRTIO_BLK_F_SEG_MAX
virtio-blk: abstract a function named virtio_blk_op_one_segment to handle r/w request
virtio-blk: split large IO according to size_max
Igor Mammedov (2):
pci: reserve resources for pcie-pci-bridge to fix regressed hotplug on q35
pci: let firmware reserve IO for pcie-pci-bridge
Florian Larysch (1):
nvme: fix LBA format data structure
Gerd Hoffmann (1):
svgamodes: add standard 4k modes
Jan Beulich via SeaBIOS (1):
nvme: avoid use-after-free in nvme_controller_enable()
next reply other threads:[~2022-03-02 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 2:19 Kevin O'Connor [this message]
2022-03-15 7:28 ` [ANNOUNCE] SeaBIOS 1.16.0 Michael Tokarev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yh7UGn7Km6CJM2MG@morn \
--to=kevin@koconnor.net \
--cc=coreboot@coreboot.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.