Index: sys/dev/pci/pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.2021
diff -u -p -r1.2021 pcidevs
--- sys/dev/pci/pcidevs 7 Feb 2023 07:10:43 - 1.2021
+++ sys/dev/pci/pcidevs 13 Feb 2023 10:06:56
> Date: Mon, 13 Feb 2023 13:08:54 +0300
> From: Vitaliy Makkoveev
What makes you think this is a PEX 8311? The data sheet I found has
the PCI device ID down as 0x8311, althogh this can be changed by
programming the EEPROM.
> Index: sys/dev/pci/pcidevs
> =
This isn't sorted by device id and looks wrong. Almost all the other
PLX entries have a device id that matches the name.
The chip is marked as PEX 8311?
On Mon, Feb 13, 2023 at 01:08:54PM +0300, Vitaliy Makkoveev wrote:
> Index: sys/dev/pci/pcidevs
> =
On Mon, Feb 13, 2023 at 11:22:36AM +0100, Mark Kettenis wrote:
> > Date: Mon, 13 Feb 2023 13:08:54 +0300
> > From: Vitaliy Makkoveev
>
> What makes you think this is a PEX 8311? The data sheet I found has
> the PCI device ID down as 0x8311, althogh this can be changed by
> programming the EEPROM
On Mon, Feb 13, 2023 at 09:35:17PM +1100, Jonathan Gray wrote:
> This isn't sorted by device id and looks wrong. Almost all the other
> PLX entries have a device id that matches the name.
>
> The chip is marked as PEX 8311?
>
Sure. I checked datasheets, PLX used this PID for RDK kit. Meanwhile