Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 May 2020 16:08:59 +0000
From:      myfreeweb <greg@unrelenting.technology>
To:        Dan Kotowski <dan.kotowski@a9development.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: FreeBSD on Layerscape/QorIQ LX2160X
Message-ID:  <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology>
In-Reply-To: <lTA1kWV3G-C1BCa0EF16x8q-YKR8dycGmQz45JrqAMwi1VKmzeR8NwYKGYUoOohz3BwPKElbUtVetcfXzI-u7Lwu7VzDCBqkCl9RXkaVsP4=@a9development.com>
References:  <fn58k-44ZAkuwnDdytVzV-cLaB9amYMgZWydbpR_muUcKNZwohKqn9zFxqqw_Vz8Ij8L8yOSv0XhefrcTSo_bSYSOe5_7wcjoBWl8Q2dDVM=@a9development.com> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com> <664db38a87ea8803be72af9738534994@unrelenting.technology> <b5105ce888b7a91eff50ec9118a910a8@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <ShdSNL8XDgj0KtPR4v8nn1ohjVssrnoUQGwNL-gHOpylio7Eo5J_WjA2Ko9YjV5md64MeFz017Ts01KUnpJa3Xpw4y_PncL4e5cfUcotRWM=@a9development.com> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <lTA1kWV3G-C1BCa0EF16x8q-YKR8dycGmQz45JrqAMwi1VKmzeR8NwYKGYUoOohz3BwPKElbUtVetcfXzI-u7Lwu7VzDCBqkCl9RXkaVsP4=@a9development.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On May 31, 2020 4:00:22 PM UTC, Dan Kotowski <dan=2Ekotowski@a9development=
=2Ecom> wrote:
>> > > I've sent a link to a known firmware build before:
>> > > https://drive=2Egoogle=2Ecom/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvE=
rK/view
>> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe?
>> >
>> > I decided to go back to the UEFI sources and have found some differen=
ces that I think need to be reconciled before moving forward=2E That said, =
I'm not an ACPI wizard by any means - for me it's low-level mage spells at =
best=2E=2E=2E
>> > In https://github=2Ecom/SolidRun/edk2-platforms we have 2 different b=
ranches that SolidRun seems to use:
>> >
>> > 1=2E  LSDK-19=2E09-sr
>> > 2=2E  master-lx2160a
>> >
>> > I've been building from the latter branch, but found some significant=
 differences in the former that I think may be important to merge in=2E
>>
>> To me it seems like 19=2E09 is just outdated and doesn't have any benef=
its=2E Ask the solidrun people to be sure=2E
>>
>> Either way, nothing here would fix the interrupt bug=2E It's our bug si=
nce NetBSD works fine :(
>
>Any thoughts on the "Poll mode" comment below from the dts? We're still n=
ot seeing any of the PHYs in either BSD=2E
>
>```
>&emdio1 {
>  rgmii_phy1: ethernet-phy@1 {
>    /* AR8035 PHY - "compatible" property not strictly needed */
>    compatible =3D "ethernet-phy-id004d=2Ed072";
>    reg =3D <0x1>;
>    /* Poll mode - no "interrupts" property defined */
>  };
>};
>```

Why are you looking at Ethernet stuff?
We do not have a driver for NXP's NIC in any BSD=2E

(I do wonder if the Semihalf work on the Layerscape family would eventuall=
y include Ethernet=2E=2E)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E21DEB1-0C86-41CD-BE89-FBF2EF45443C>