public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] pci: pci_mvebu: ignore the local device
Date: Fri, 10 May 2019 13:44:01 +0200	[thread overview]
Message-ID: <20190510134401.03701045@nic.cz> (raw)
In-Reply-To: <d3e9cedb-8ea7-4840-a977-154bee2377b7@denx.de>

On Fri, 10 May 2019 10:15:25 +0200
Stefan Roese <sr@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.

  reply	other threads:[~2019-05-10 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  2:56 [U-Boot] [PATCH 1/1] pci: pci_mvebu: ignore the local device Marek Behún
2019-05-10  8:10 ` Chris Packham
2019-05-10  8:15 ` Stefan Roese
2019-05-10 11:44   ` Marek Behun [this message]
2019-05-10 12:58     ` Stefan Roese
2019-05-12 20:40     ` Chris Packham
2019-05-12 21:02       ` Marek Behun

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=20190510134401.03701045@nic.cz \
    --to=marek.behun@nic.cz \
    --cc=u-boot@lists.denx.de \
    /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