public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] pciutils: Update to version 3.7.0
Date: Fri, 04 Feb 2022 12:05:14 +0000	[thread overview]
Message-ID: <0e576bcc-5254-b53a-24ec-139cfbd271c2@ipfire.org> (raw)
In-Reply-To: <20220128130814.3417558-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 6541 bytes --]

Hello Adolf,

I regret to inform you that I worked on the same thing.

Comparing both patches (see https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=34a98832ee5ec33ef75f4732dfed003e9b76185c
for mine), the MD5 checksum differs: Yours is e6e20482b4f25c5186e6a753c5edc361, while
mine is 51554c538b5a57b61123326e14ea28a1.

I will investigate into this and report back later.

Thanks, and best regards,
Peter Müller


> - Update from 3.5.6 (2017) to 3.7.0 (2020)
> - Update of rootfile
> - Changelog
>     2020-05-31  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.7.0.
> 	* Added or improved the following capabilities: Designated Vendor-Specific,
> 	  Compute eXpress Link, Resizable BARs, VF Resizable BARs, Link
> 	  Capabilities 2, Link Status 2.
> 	* On Linux, lspci can show IOMMU groups.
> 	* setpci can be asked to skip bus scan and operate on a device
> 	  completely specified by its domain/bus/dev/func address. This
> 	  involved major internal cleanup.
> 	* The above feature of setpci uses the pci_get_dev() function,
> 	  which obtains a struct pci_dev without doing a bus scan. This was
> 	  always possible, but apparently little used, because back-ends
> 	  frequently choked when operating on such devices. Fixed a lot
> 	  of minor bugs related to this.
> 	* Also, back-ends which do not support domains now correctly fail when
> 	  trying to access devices outside domain 0.
> 	* Semantics of pci_fill_info() and pci_dev->known_fields was underspecified,
> 	  which lead to inconsistencies between back-ends. Improved documentation
> 	  to give a more precise definition and updated all back-ends to conform
> 	  to it. Most importantly, pci_dev->known_fields shows all fields requested
> 	  over the lifetime of the pci_dev, but never those which are not supported
> 	  by the back-end.
> 	* As usually, updated pci.ids to the current snapshot of the database.
>     2020-01-25  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.6.4.
> 	* A new back-end for the GNU Hurd was contributed by Joan Lledó.
> 	* When printing VPD item identifiers, non-ASCII characters are escaped.
>     2020-01-22  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.6.3.
> 	* `lspci -t' (tree mode) can be combined with `-s' to show a sub-tree.
> 	  We also fixed potential buffer overflows in the tree dumper.
> 	* Cleaned messy code for dumping of I/O, memory, and ROM regions.
> 	  This helped fixing a bug, which caused some 64-bit regions to be
> 	  reported as virtual. All flags are now printed after the address
> 	  (previously, "[virtual]" and "[enhanced]" were before it for no good
> 	  reason).
> 	* Added pci_find_cap_nr() to the library, which handles capabilities
> 	  which occur multiple times in a single device.
> 	* Minor improvements in printing of PCIe capabilities.
> 	* We now decode the Multicast and Secondary PCI Express extended
> 	  capabilities.
> 	* The list of capability names available to setpci was updated.
> 	* Minor bugs were fixed in FreeBSD and Solaris ports.
> 	* We now prefer HTTPS URLs in all documentation
> 	* The pci.ids file has a man page.
> 	* As usually, updated pci.ids to the current snapshot of the database.
>     2018-08-12  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.6.2.
> 	* Added "-P" and "-PP" switches to lspci, which display the path
> 	  through bridges to each device.
> 	* Fixed a couple of bugs in computation of bus topology. It was
> 	  previously used only for the tree display, but we re-use it for
> 	  computing the paths.
> 	* As usually, updated pci.ids to the current snapshot of the database.
>     2018-07-12  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.6.1.
> 	* Fixed compilation issues on Linux systems with MUSL libc.
>     2018-06-30  Martin Mares <mj(a)ucw.cz>
>     * Released as 3.6.0.
> 	* BARs reported by the OS, but not set on the device itself are
> 	  reliably marked with "[virtual]".
> 	* Library: Introduced a generic mechanism of string properties. This
> 	  avoids lots of special cases and makes ABI compatibility easier.
> 	* On Linux systems with OpenFirmware, report corresponding device tree nodes
> 	  as device properties.
> 	* VPD decoder knows several non-standard extensions.
> 	* When PCIe link speed is less than the maximum supported by the
> 	  device, it is explicitly marked as "downgraded".
> 	* Several new capabilities are not decoded yet, but at least their
> 	  names are printed.
> 	* The Null capability is easily decoded.
> 	* Formatting of several capabilities was cleaned up.
> 	* The VGA16 bit in the bridge control register is now supported.
> 	* Added a port to SylixOS. Thanks to YuJian Gong for contribution.
> 	* Added a port to DOS/DJGPP. Thanks to Rudolf Marek for contribution.
> 	* The order in which back-ends are probed was decoupled from the
> 	  internal back-end IDs. This helps, because new back-ends must have
> 	  their ID allocated at the end to keep the ABI, but they might need
> 	  to be probed earlier.
> 	* The fbsd-device back-end should work again.
> 	* Fixed a couple of bugs. Most notably, DeviceName was not printed.
> 	* As usually, updated pci.ids to the current snapshot of the database.
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>  config/rootfiles/common/pciutils | 2 +-
>  lfs/pciutils                     | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/config/rootfiles/common/pciutils b/config/rootfiles/common/pciutils
> index da35ef6a1..17a3ede66 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.5.6
> +lib/libpci.so.3.7.0
>  sbin/update-pciids
>  #usr/include/pci
>  #usr/include/pci/config.h
> diff --git a/lfs/pciutils b/lfs/pciutils
> index 2068c5a0c..2bd5d3c5d 100644
> --- a/lfs/pciutils
> +++ b/lfs/pciutils
> @@ -24,10 +24,10 @@
>  
>  include Config
>  
> -VER        = 3.5.6
> +VER        = 3.7.0
>  
>  THISAPP    = pciutils-$(VER)
> -DL_FILE    = $(THISAPP).tar.gz
> +DL_FILE    = $(THISAPP).tar.xz
>  DL_FROM    = $(URL_IPFIRE)
>  DIR_APP    = $(DIR_SRC)/$(THISAPP)
>  TARGET     = $(DIR_INFO)/$(THISAPP)
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_MD5 = 63b347d2bb5719b7769c03a1bb72a5b7
> +$(DL_FILE)_MD5 = e6e20482b4f25c5186e6a753c5edc361
>  
>  install : $(TARGET)
>  

  reply	other threads:[~2022-02-04 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 13:08 Adolf Belka
2022-02-04 12:05 ` Peter Müller [this message]
2022-02-04 12:43   ` Adolf Belka
2022-02-04 16:57     ` Michael Tremer
2022-02-06 10:47     ` Peter Müller

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=0e576bcc-5254-b53a-24ec-139cfbd271c2@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