lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Mon, 6 Jul 2020 12:22:17 +0200
From:   Arnd Bergmann <>
To:     Daniel Gutson <>
Cc:     Derek Kiernan <>,
        Greg Kroah-Hartman <>,
        Mauro Carvalho Chehab <>,
        "" <>,
        Richard Hughes <>,
        Alex Bazhaniuk <>,
        linux-pci <>
Subject: Re: [PATCH] SPI LPC information kernel module

On Fri, Jul 3, 2020 at 10:43 PM Daniel Gutson <> wrote:

> After analyzing the intel-spi driver, I came up to these observations that led me conclude that it is not what I need to use:
> * Some SPI Controllers have 0xFFFF as their VID DID bytes in the PCI config space. This causes that the PCI devices enumeration doesn't include them,
> and thus a PCI device driver won't be probed even despite listing the DID that the datasheet specifies. I effectively confirmed this by doing a PCI device driver and
> trying the intel-spi in systems with this characteristic. In short, the intel-spi driver doesn't work with these systems.

Maybe this part can be handled with a fixup in drivers/pci that
changes the effective
PCI device ID on the systems that do need to access the device.

Adding the PCI mailing list for other ideas. Basically it sounds like
the BIOS has
intentionally configured the SPI-NOR device to be hidden from PCI probing to
prevent operating systems from accessing it, but you want to ignore that and
access it anyway, correct?


Powered by blists - more mailing lists