linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space
Date: Tue, 18 Dec 2018 21:37:16 +0100	[thread overview]
Message-ID: <20181218213716.70d27f1f@windsurf> (raw)
In-Reply-To: <CAEzXK1ryTQ5sbUSuZoq36ss=Z7ewLegaxsXtvsNOGqHyTQibmg@mail.gmail.com>

Hello,

On Tue, 18 Dec 2018 15:42:34 +0000, Luís Mendes wrote:

> Thanks a lot for your quick reply and patch, but unfortunately the
> problem remains the same with the patch applied.

Gaah, too bad. A shot in the dark sometimes works, sometimes not.

> How can I help to further pin down the issue?

Could you post the output of:

lspci -vvv -xxx

with the "PCI: mvebu: Convert to PCI emulated bridge config space"
patch applied and reverted, and send the result ? This would allow me
to look at the differences in the configuration space exposed by the
emulated bridge and hopefully see which one might cause the regression.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-18 20:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEzXK1o9L-bVRGBpAo+a_wYqXZh6_zuebF221Bd8=b-DTL1Q9g@mail.gmail.com>
     [not found] ` <CAEzXK1po4ik1oHdwVvVMWEqh8KMdAMY7sxv9OR2bYs54qV6EyA@mail.gmail.com>
2018-12-18 13:42   ` Fwd: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space Luís Mendes
2018-12-18 13:47 ` Thomas Petazzoni
2018-12-18 14:34   ` Thomas Petazzoni
2018-12-18 15:42     ` Luís Mendes
2018-12-18 20:37       ` Thomas Petazzoni [this message]
2018-12-18 23:13         ` Luís Mendes
2019-01-08 10:48           ` Thomas Petazzoni
     [not found]             ` <CAEzXK1oQd1YNZ5pyNXA76h-3CbBRxmTke=Z-SRusyfqL=Wd8eA@mail.gmail.com>
2019-01-09  8:15               ` Thomas Petazzoni
     [not found]                 ` <CAEzXK1oHqOb3pojfX7JqrirxjOFj=UZZfi6tNNO4y6yC3u9LAA@mail.gmail.com>
2019-02-04 11:09                   ` Luís Mendes
2019-02-12 13:41                     ` Thomas Petazzoni
2019-02-13 11:34                       ` Luís Mendes
2019-02-13 12:33                         ` Thomas Petazzoni
2019-02-13 13:24                           ` Luís Mendes

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=20181218213716.70d27f1f@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=luis.p.mendes@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).