Le 25/06/2024 à 13:31, Etienne Dublé a écrit :
The bus addresses should be isolated to each pci controller if I am not
mistaken, so changing the bus address was probably just done as a
workaround because of some other unknown bug.
OK.
Hum, could be an issue in pci core of U-Boot that expec
Hello Jonas,
Le 25/06/2024 à 12:46, Jonas Karlman a écrit :
Ahh, linux is still missing a patch to be able to use full address ranges
as a root complex.
Will re-run some tests on my R5C on both u-boot and linux to see if I can
replicate your issue.
OK.
To use the second interface in u-boot,
Hello Etienne,
On 2024-06-25 12:12, Etienne Dublé wrote:
>
> Hello Jonas,
>
> Le 25/06/2024 à 10:29, Jonas Karlman a écrit :
>> I do not understand the need for such/this patch. The changed address is
>> the internal io address that is shared with the pci controller and
>> devices.
>>
>> Do you
Hello Jonas,
Le 25/06/2024 à 10:29, Jonas Karlman a écrit :
I do not understand the need for such/this patch. The changed address is
the internal io address that is shared with the pci controller and
devices.
Do you have any issue in linux or is it only in U-Boot?, I suspect this
change is on
> Date: Tue, 25 Jun 2024 10:29:48 +0200
> From: Jonas Karlman
Hi Jonas,
> Hi Etienne,
>
> On 2024-06-25 08:47, Etienne Dublé wrote:
> > Hi Quentin,
> >
> > Le 24/06/2024 à 15:15, Quentin Schulz a écrit :
> >> Hi Etienne,
> >>
> >> On 6/24/24 2:40 PM, ETIENNE DUBLE wrote:
> >>> One of the PCI r
Hi Etienne,
On 2024-06-25 08:47, Etienne Dublé wrote:
> Hi Quentin,
>
> Le 24/06/2024 à 15:15, Quentin Schulz a écrit :
>> Hi Etienne,
>>
>> On 6/24/24 2:40 PM, ETIENNE DUBLE wrote:
>>> One of the PCI ranges was wrong in this device tree.
>>> When testing with a FriendlyElec Nanopi R5C board, the
Hi Quentin,
Le 24/06/2024 à 15:15, Quentin Schulz a écrit :
Hi Etienne,
On 6/24/24 2:40 PM, ETIENNE DUBLE wrote:
One of the PCI ranges was wrong in this device tree.
When testing with a FriendlyElec Nanopi R5C board, the
2nd ethernet interface (labelled "wan") was not working
in u-boot because
Hi Etienne,
On 6/24/24 2:40 PM, ETIENNE DUBLE wrote:
One of the PCI ranges was wrong in this device tree.
When testing with a FriendlyElec Nanopi R5C board, the
2nd ethernet interface (labelled "wan") was not working
in u-boot because of that.
With the correct value (found in FriendlyElec's dow
One of the PCI ranges was wrong in this device tree.
When testing with a FriendlyElec Nanopi R5C board, the
2nd ethernet interface (labelled "wan") was not working
in u-boot because of that.
With the correct value (found in FriendlyElec's downstream
u-boot repository), this 2nd ethernet interface
9 matches
Mail list logo
