Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1275875 > unrolled thread

Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

Started byKhalid Aziz <khalid.aziz@oracle.com>
First post2015-11-23 22:40 +0100
Last post2015-11-24 03:40 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4 Khalid Aziz <khalid.aziz@oracle.com> - 2015-11-23 22:40 +0100
    Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4 Yinghai Lu <yinghai@kernel.org> - 2015-11-24 03:40 +0100

#1275875 — Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

FromKhalid Aziz <khalid.aziz@oracle.com>
Date2015-11-23 22:40 +0100
SubjectRe: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4
Message-ID<qy706-7p3-31@gated-at.bofh.it>
On Fri, 2015-10-30 at 18:53 -0700, Yinghai Lu wrote:
> On Fri, Oct 30, 2015 at 2:47 PM, Khalid Aziz <khalid.aziz@oracle.com> 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 0000:04:00.0: can't claim BAR 6 [mem 0x84000000000-0x8400000ffff]:
> > address conflict with 0000:04:00.0 [mem 0x84000000000-0x840007fffff]
> 
> PCI: scan_bus[/pci@400/pci@1/pci@0/pci@0/pci@0] bus no 4
>   * /pci@400/pci@1/pci@0/pci@0/pci@0/display@0
>     create device, devfn: 0, type: display
>     class: 0x30000 device name: 0000:04:00.0
>     parse addresses (80 bytes) @ fff8001fffe34f40
>   start: 84000000000, end: 840007fffff, i: 10
>   start: 84000800000, end: 8400081ffff, i: 14
>   start: 85100000000, end: 8510000007f, i: 18
>   start: 84000000000, end: 8400000ffff, i: 30
> 
> so the BAR 6 the ROM bar is overlapping with BAR0.
> and the ROM bar get rejected.
> 
> Looks like only the device BAR6 is not assigned form OF?
> 

Hi Yinghai,

Any progress on this? Do you need any more information from me?

Thanks,
Khalid

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1276026

FromYinghai Lu <yinghai@kernel.org>
Date2015-11-24 03:40 +0100
Message-ID<qybGq-1Y4-21@gated-at.bofh.it>
In reply to#1275875
On Mon, Nov 23, 2015 at 1:31 PM, Khalid Aziz <khalid.aziz@oracle.com> 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 working with
this patch set.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web