[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXUhvG2Jub3sbBxyCERVbt-L22+O+mcZ_HWEVQ_QaRawA@mail.gmail.com>
Date: Tue, 18 Feb 2014 10:52:54 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Steven Newbury <steve@...wbury.org.uk>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: pci-3.14 resource alloc
On Tue, Feb 18, 2014 at 2:08 AM, Steven Newbury <steve@...wbury.org.uk> wrote:
>> >
>> > 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.
>>
>
> 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.
I had the busn_res_alloc patches in the branch.
There is some changes about acpi dock driver from Rafael in recent
kernels. Maybe Rafael could suggest which commit could cause problem,
then you could try revert them on top of branch.
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists