> > We see that similar test is passing in x86 machine, where function one
> > requesting 1GB BAR's is failing, but function two requesting BAR's
> > with 16byte is getting assigned BAR's.
> >
> > To my knowledge on x86 BIOS assigns resources, or will kernel assign
> > reosurces on x86 ? If
> > We see that similar test is passing in x86 machine, where function one
> > requesting 1GB BAR's is failing, but function two requesting BAR's
> > with 16byte is getting assigned BAR's.
> >
> > To my knowledge on x86 BIOS assigns resources, or will kernel assign
> > reosurces on x86 ? If
On Wed, Jul 27, 2016 at 06:33:29AM +, Bharat Kumar Gogada wrote:
> > Your system host bridge: has resource
> > pci_bus :00: root bus resource [mem 0xe010-0xefff] pci_bus
> > :00: root bus resource [mem 0x6-0x7 pref] then one pci
> > bridge:
> > pci :00:00.0
On Wed, Jul 27, 2016 at 06:33:29AM +, Bharat Kumar Gogada wrote:
> > Your system host bridge: has resource
> > pci_bus :00: root bus resource [mem 0xe010-0xefff] pci_bus
> > :00: root bus resource [mem 0x6-0x7 pref] then one pci
> > bridge:
> > pci :00:00.0
> Your system host bridge: has resource
> pci_bus :00: root bus resource [mem 0xe010-0xefff] pci_bus
> :00: root bus resource [mem 0x6-0x7 pref] then one pci
> bridge:
> pci :00:00.0
> then :01:00.0 have four bars:
> pci :01:00.0: BAR 0: [mem size
> Your system host bridge: has resource
> pci_bus :00: root bus resource [mem 0xe010-0xefff] pci_bus
> :00: root bus resource [mem 0x6-0x7 pref] then one pci
> bridge:
> pci :00:00.0
> then :01:00.0 have four bars:
> pci :01:00.0: BAR 0: [mem size
On Tue, Jul 26, 2016 at 8:43 AM, Bharat Kumar Gogada
wrote:
>> > > We have only one End point connected to our root port.
>> > >
>> > > Here is the log:
>> > > [2.319289] nwl-pcie fd0e.pcie: Link is UP
>> > > [2.319332] PCI host bridge
On Tue, Jul 26, 2016 at 8:43 AM, Bharat Kumar Gogada
wrote:
>> > > We have only one End point connected to our root port.
>> > >
>> > > Here is the log:
>> > > [2.319289] nwl-pcie fd0e.pcie: Link is UP
>> > > [2.319332] PCI host bridge /amba/pcie@fd0e ranges:
>> > > [2.319349]
Adding yinghai lu.
> > > > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> > > >
> > > > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > > > > Hi Bharat,
> > > > >
> > > > > On
Adding yinghai lu.
> > > > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> > > >
> > > > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > > > > Hi Bharat,
> > > > >
> > > > > On
> Subject: RE: Why does BIOS assign memory to 16 byte BAR
>
> > Subject: RE: Why does BIOS assign memory to 16 byte BAR
> >
> > > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> > >
> > > On Fri, Jul 22, 2016 at 10:15:46AM
> Subject: RE: Why does BIOS assign memory to 16 byte BAR
>
> > Subject: RE: Why does BIOS assign memory to 16 byte BAR
> >
> > > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> > >
> > > On Fri, Jul 22, 2016 at 10:15:46AM
> Subject: RE: Why does BIOS assign memory to 16 byte BAR
>
> > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> >
> > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > > Hi Bharat,
> > >
> > > On Fri, Jul 22,
> Subject: RE: Why does BIOS assign memory to 16 byte BAR
>
> > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> >
> > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > > Hi Bharat,
> > >
> > > On Fri, Jul 22,
> Subject: Re: Why does BIOS assign memory to 16 byte BAR
>
> On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > Hi Bharat,
> >
> > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > > Hi,
> > >
> > > I'm
> Subject: Re: Why does BIOS assign memory to 16 byte BAR
>
> On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > Hi Bharat,
> >
> > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > > Hi,
> > >
> > > I'm
On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> Hi Bharat,
>
> On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > Hi,
> >
> > I'm observing that on x86 BIOS successfully assigns memory if an End point
> > requests
> > BAR of size 16byte.
> >
> > But as
On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> Hi Bharat,
>
> On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > Hi,
> >
> > I'm observing that on x86 BIOS successfully assigns memory if an End point
> > requests
> > BAR of size 16byte.
> >
> > But as
Hi Bharat,
On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> Hi,
>
> I'm observing that on x86 BIOS successfully assigns memory if an End point
> requests
> BAR of size 16byte.
>
> But as per Spec:
> The minimum memory address range requested by a BAR is 128 bytes.
Can
Hi Bharat,
On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> Hi,
>
> I'm observing that on x86 BIOS successfully assigns memory if an End point
> requests
> BAR of size 16byte.
>
> But as per Spec:
> The minimum memory address range requested by a BAR is 128 bytes.
Can
Hi,
I'm observing that on x86 BIOS successfully assigns memory if an End point
requests
BAR of size 16byte.
But as per Spec:
The minimum memory address range requested by a BAR is 128 bytes.
Why BIOS is successfully allocating region to 16 byte BAR requests?
Please let me know if my
Hi,
I'm observing that on x86 BIOS successfully assigns memory if an End point
requests
BAR of size 16byte.
But as per Spec:
The minimum memory address range requested by a BAR is 128 bytes.
Why BIOS is successfully allocating region to 16 byte BAR requests?
Please let me know if my
22 matches
Mail list logo