On Tue, Oct 20, 2015 at 5:03 PM, Yinghai Lu wrote:
>> The failing T4 booted up with updated patches.
>>
>
> Thanks, will post updated patch2 and patches3 and patch 4 with
> pcibios_bus_to_resource as Bjorn requested.
Please double test attached three patches that should replace patch 2, 3, 4.
esp
On Tue, Oct 20, 2015 at 4:51 PM, Khalid Aziz wrote:
> On 10/20/2015 02:34 PM, Yinghai Lu wrote:
>>
>> On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz
>> wrote:
I don't want to argue about pci_resource_to_user() right now, so I
guess you can just panic if the mem64 offset is different
On 10/20/2015 02:34 PM, Yinghai Lu wrote:
On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz wrote:
I don't want to argue about pci_resource_to_user() right now, so I
guess you can just panic if the mem64 offset is different from the
mem32 offset. But you should at least add a comment about why you'
On 10/20/2015 02:34 PM, Yinghai Lu wrote:
On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz wrote:
I don't want to argue about pci_resource_to_user() right now, so I
guess you can just panic if the mem64 offset is different from the
mem32 offset. But you should at least add a comment about why you'
On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz wrote:
>> I don't want to argue about pci_resource_to_user() right now, so I
>> guess you can just panic if the mem64 offset is different from the
>> mem32 offset. But you should at least add a comment about why you're
>> doing that. Otherwise it look
On 10/20/2015 01:54 PM, Bjorn Helgaas wrote:
On Thu, Oct 08, 2015 at 02:38:21PM -0700, Yinghai Lu wrote:
After we add 64bit mmio parsing, we got some "no compatible bridge window"
warning on anther new model that support 64bit resource.
It turns out that we can not use mem_space.start as 64bit
On Thu, Oct 08, 2015 at 02:38:21PM -0700, Yinghai Lu wrote:
> After we add 64bit mmio parsing, we got some "no compatible bridge window"
> warning on anther new model that support 64bit resource.
>
> It turns out that we can not use mem_space.start as 64bit mem space
> offset, aka mem_space.start
On Thu, Oct 08, 2015 at 02:38:21PM -0700, Yinghai Lu wrote:
> After we add 64bit mmio parsing, we got some "no compatible bridge window"
> warning on anther new model that support 64bit resource.
>
> It turns out that we can not use mem_space.start as 64bit mem space
> offset, aka mem_space.start
On Thu, 2015-10-08 at 14:38 -0700, Yinghai Lu wrote:
> After we add 64bit mmio parsing, we got some "no compatible bridge window"
> warning on anther new model that support 64bit resource.
>
> It turns out that we can not use mem_space.start as 64bit mem space
> offset, aka mem_space.start != offs
9 matches
Mail list logo
