From: Steven Newbury <steve@snewbury.org.uk>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pci-3.14 resource alloc
Date: Tue, 18 Feb 2014 10:08:27 +0000 [thread overview]
Message-ID: <1392718107.15829.12.camel@artifact> (raw)
In-Reply-To: <CAE9FiQV3H_nxH0gxcM0kW4uLm6b_qmHT9hRQUVY_4xPqjpvMtA@mail.gmail.com>
On Fri, 2014-02-14 at 11:11 -0800, Yinghai Lu wrote:
> On Fri, Feb 14, 2014 at 7:46 AM, Steven Newbury <steve@snewbury.org.uk> wrote:
> >>
> >> Oh, never mind! I didn't notice pref_bar has been renamed to
> >> assign_pref_bars. It's working now! :)
> >
> > There's no pci bridge/bus hotplug though. Docking doesn't reveal the
> > pci-e->pci bridge or the (radeon) devices on the other side.
>
> oh, no. could be other regression in linus tree or pci/next.
>
Sorry about taking a while to get back to you.
Previously I needed the busn work to get it working, this was included
in the resource-alloc branch. It never worked on mainline, the bridge
used to show up but never get scanned. Now it's not showing up at all
on hotplug. It could be a dock driver regression.
> Can you check if linus tree could reveal pci-e->pci bridge?
>
I'll give it a go.
> or do you use iommu/dmar with the system?
>
No, the only unusual option is I use pci=nocrs since the bios is
completely ignorant of support for 64bit BARs.
> Thanks
>
> Yinghai
next prev parent reply other threads:[~2014-02-18 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1390773698.3450.12.camel@artifact>
[not found] ` <CAE9FiQVD=oVHM5WJgSJ5cNpXZ1NYy9E_pcGWfjKnmD9OZoHHsw@mail.gmail.com>
[not found] ` <1391643656.1067.1.camel@artifact>
2014-02-14 0:50 ` pci-3.14 resource alloc Yinghai Lu
[not found] ` <z9zi9m.n0zpxd.1hgeaud-qmf@mail.snewbury.org.uk>
[not found] ` <i9nn22.n0zs79.1hgeaud-qmf@mail.snewbury.org.uk>
[not found] ` <1392392764.3520.11.camel@devel-n900>
2014-02-14 19:11 ` Yinghai Lu
2014-02-18 10:08 ` Steven Newbury [this message]
2014-02-18 13:59 ` Bjorn Helgaas
2014-02-18 14:37 ` Bjorn Helgaas
2014-02-18 17:31 ` Steven Newbury
2014-02-18 18:52 ` Yinghai Lu
2014-02-18 22:29 ` Rafael J. Wysocki
2014-02-19 9:11 ` Steven Newbury
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=1392718107.15829.12.camel@artifact \
--to=steve@snewbury.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/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).