HEADS UP: Cavium ThunderX support in the tree

Zbigniew Bodek zbb at semihalf.com
Fri Nov 6 14:52:45 UTC 2015


2015-11-06 15:45 GMT+01:00 Andrew Turner <andrew at fubar.geek.nz>:
> On Fri, 6 Nov 2015 13:10:10 +0100
> Zbigniew Bodek <zbb at semihalf.com> wrote:
>
>> 2015-11-06 12:36 GMT+01:00 Andrew Turner <andrew at fubar.geek.nz>:
>> > On Fri, 6 Nov 2015 12:23:11 +0100
>> > Zbigniew Bodek <zbb at semihalf.com> wrote:
>> >> Secondly, EFI that runs on the board needs to pass the correct DTB
>> >> to the kernel (it has to have PCIB, BGX, MDIO, PHYs nodes and they
>> >> need to be in the correct order [MDIO needs to attach before
>> >> BGX]).
>> > If this is the case the code is broken. It should just work with
>> > the vendor dtb and GENERIC.
>>
>> Thanks for quick evaluation but please see comment below.
>>
>> >
>> > We already have to handle this in other parts of the code by having
>> > the dependent drivers on an earlier pass than later drivers.
>>
>> MDIO is a platform device whereas BGX, NICPF (physical function) and
>> NICVF (virtual function) are devices on PCI.
>> Therefore if the PCIB is placed prior to MDIO in DTB all devices on
>> this PCI bridge will be attached before MDIO is attached.
>> As far as I know there is no straightforward way to create a logical
>> relation between device on PCI and platform devices enumerated using
>> DTB.
>> That is why we asked Cavium to change the order in their DTBs.
>> Of course if you know how to workaround that I would be happy to apply
>> this change to "unbreak" the existing code.
>
> No need, I've fixed it in r290448.
>
> Andrew

OK. Thanks!

Best regards
zbb


More information about the freebsd-arm mailing list