On 10.05.19 13:44, Marek Behun wrote:
On Fri, 10 May 2019 10:15:25 +0200
Stefan Roese <s...@denx.de> wrote:

On 10.05.19 04:56, Marek BehĂșn wrote:
The local device (host "bridge"?) on pci_mvebu controller reports
PCI_CLASS_MEMORY_OTHER in the class register.

This does not work in U-Boot, because U-Boot then tries to autoconfigure
this device in pci_auto.c. This causes the real connected PCIe device
not to work (in U-Boot nor in Linux).

What exactly does not work or is the issue here with the current
implementation in Linux? I'm asking, since we have not noticed any
issues here?

ath10k firmware fails to load for network device.
SATA device timeouts on a PCIe SATA expander.
As if some PCIe I/O did not work. The devices are still enumerated and
recognized by Linux, but simply won't work. Nor in U-Boot.

I see. Strange that we did not see any issues on our board (or
other users). I'll try to pull this patch into this upcoming
release though.

Thanks,
Stefan
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to