On Tue, Dec 1, 2015 at 1:23 PM, Khalid Aziz wrote:
> The device does work with this patch.
Good.
> Doesn't this warning mean BAR6
> resources could not be reserved which means the device driver may not be
> able to get the BAR6 resource at some point if another device grabs the
> unreserved reso
On 11/23/2015 07:39 PM, Yinghai Lu wrote:
On Mon, Nov 23, 2015 at 1:31 PM, Khalid Aziz wrote:
Looks like only the device BAR6 is not assigned form OF?
Any progress on this? Do you need any more information from me?
Should be one warning about this device in that system.
We don't need to do
On Mon, Nov 23, 2015 at 1:31 PM, Khalid Aziz wrote:
>> Looks like only the device BAR6 is not assigned form OF?
>
> Any progress on this? Do you need any more information from me?
Should be one warning about this device in that system.
We don't need to do anything about it if the device is worki
On Fri, 2015-10-30 at 18:53 -0700, Yinghai Lu wrote:
> On Fri, Oct 30, 2015 at 2:47 PM, Khalid Aziz wrote:
> >
> > I applied patches 1-8 and 11-16 to 4.3.0-rc7 to test on sparc platforms. I
> > am seeing a "can't claim BAR" message on a T4:
> >
> > pci :04:00.0: can't claim BAR 6 [mem 0x84
On Sat, 2015-10-31 at 14:51 -0400, David Miller wrote:
> This is the way OF seems to work.
>
> It maps all of the ROMs essentially to the same address range, but
> only enables one at a time as it inspects the ROMs and builds the
> device tree during power-on.
>
> Then it makes sure all of them a
From: Yinghai Lu
Date: Fri, 30 Oct 2015 18:53:23 -0700
> On Fri, Oct 30, 2015 at 2:47 PM, Khalid Aziz wrote:
>>
>> I applied patches 1-8 and 11-16 to 4.3.0-rc7 to test on sparc platforms. I
>> am seeing a "can't claim BAR" message on a T4:
>>
>> pci :04:00.0: can't claim BAR 6 [mem 0x840
On Fri, Oct 30, 2015 at 2:47 PM, Khalid Aziz wrote:
>
> I applied patches 1-8 and 11-16 to 4.3.0-rc7 to test on sparc platforms. I
> am seeing a "can't claim BAR" message on a T4:
>
> pci :04:00.0: can't claim BAR 6 [mem 0x840-0x840]:
> address conflict with :04:00.0 [mem 0
Hi,
After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows
to 64-bit resources), we have several reports on resource allocation
failure, and we try to fix the problem with resource clip, and find
more problems.
One is realloc fail with two graphics cards above 4G.
One is from sparc
8 matches
Mail list logo
