From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] pciutils: Update to version 3.10.0
Date: Thu, 22 Jun 2023 21:33:00 +0000 [thread overview]
Message-ID: <fee6e821-d302-666d-9cb3-d27df0c57ea8@ipfire.org> (raw)
In-Reply-To: <20230616182434.3450975-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2990 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 3.9.0 to 3.10.0
> - Update of rootfile
> - version 3.9.0 failed to output some of the symbols. This was found as a bug in Fedora but
> also seen by some people in IPFire CU175 with flashrom where the version 3.3 symbol is
> provided.
> Fedora made a patch to resolve this issue for 3.9.0 but 3.10.0 has been released since
> then and Fedora removed the patch that was used for 2.9.0 as pciutils has had that bug
> fixed - see first item in changelog.
> - Changelog
> Released as 3.10.0.
> Fixed bug in definition of versioned symbol aliases
> in shared libpci, which made compiling with link-time
> optimization fail.
> Filters now accept "0x..." syntax for backward compatibility.
> Windows: The cfgmgr32 back-end which provides the list of devices
> can be combined with another back-end which provides access
> to configuration space.
> ECAM (Enhanced Configuration Access Mechanism), which is defined
> by the PCIe standard, is now supported. It requires root privileges,
> access to physical memory, and also manual configuration on some
> systems.
> lspci: Tree view now works on multi-domain systems. It now respects
> filters properly.
> Last but not least, pci.ids were updated to the current snapshot
> of the database. This includes overall cleanup of entries with
> non-ASCII characters in their names -- such characters are allowed,
> but only if they convey interesting information (e.g., umlauts
> in German company names, but not the "registered trade mark" sign).
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/pciutils | 2 +-
> lfs/pciutils | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/pciutils b/config/rootfiles/common/pciutils
> index 067f269f3..491bf0567 100644
> --- a/config/rootfiles/common/pciutils
> +++ b/config/rootfiles/common/pciutils
> @@ -1,7 +1,7 @@
> bin/lspci
> bin/setpci
> lib/libpci.so.3
> -lib/libpci.so.3.9.0
> +lib/libpci.so.3.10.0
> sbin/update-pciids
> #usr/include/pci
> #usr/include/pci/config.h
> diff --git a/lfs/pciutils b/lfs/pciutils
> index fdfeb4838..eb9a0b2d7 100644
> --- a/lfs/pciutils
> +++ b/lfs/pciutils
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3.9.0
> +VER = 3.10.0
>
> THISAPP = pciutils-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 59d2a151b114691980b8f0a0bfdf8e48b9e1a0a9976df6dbc94962c251d8bfc61e7bd3b0f3c47a4295f52b5df67ad0e44ed6f2e6a87728e213e4ef0b8a55c028
> +$(DL_FILE)_BLAKE2 = 2e1255eb5508c9d1339f5bc772c2592a03cae4d8d097e8939748c9bb5d5d949be53d705d1b7d903f7ea88b2abeea91e39de16e39d2f46f0a1f62f8a9e32c6faa
>
> install : $(TARGET)
>
prev parent reply other threads:[~2023-06-22 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 18:24 Adolf Belka
2023-06-22 21:33 ` Peter Müller [this message]
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=fee6e821-d302-666d-9cb3-d27df0c57ea8@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox