Date: Mon, 1 Jun 2020 02:26:04 +0200 From: Marcin Wojtas <mw@semihalf.com> To: myfreeweb <greg@unrelenting.technology> Cc: Dan Kotowski <dan.kotowski@a9development.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <CAPv3WKfEYz-2H-AvTB5=utCtP=TUEvgbaUYw9k7xFBib6KquyQ@mail.gmail.com> In-Reply-To: <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> 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> <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, niedz., 31 maj 2020 o 18:09 myfreeweb <greg@unrelenting.technology> napisa= =C5=82(a): > > > > On May 31, 2020 4:00:22 PM UTC, Dan Kotowski <dan.kotowski@a9development.= com> wrote: > >> > > I've sent a link to a known firmware build before: > >> > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/= 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 differe= nces that I think need to be reconciled before moving forward. That said, I= 'm not an ACPI wizard by any means - for me it's low-level mage spells at b= est... > >> > In https://github.com/SolidRun/edk2-platforms we have 2 different br= anches that SolidRun seems to use: > >> > > >> > 1. LSDK-19.09-sr > >> > 2. master-lx2160a > >> > > >> > I've been building from the latter branch, but found some significan= t differences in the former that I think may be important to merge in. > >> > >> To me it seems like 19.09 is just outdated and doesn't have any benefi= ts. Ask the solidrun people to be sure. > >> > >> Either way, nothing here would fix the interrupt bug. It's our bug sin= ce NetBSD works fine :( > > > >Any thoughts on the "Poll mode" comment below from the dts? We're still = not seeing any of the PHYs in either BSD. > > > >``` > >&emdio1 { > > rgmii_phy1: ethernet-phy@1 { > > /* AR8035 PHY - "compatible" property not strictly needed */ > > compatible =3D "ethernet-phy-id004d.d072"; > > 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. > > (I do wonder if the Semihalf work on the Layerscape family would eventual= ly include Ethernet..) > Yes, our work included ethernet support for the LS1046 by heavily modifying the sys/dev/dpaa driver, used by PowerPC QorIQ line. As the work was done on 11.x, nice forward port here is a challenge, we currently have no free cycles for. Anyway, LS2K uses a different IP (DPAA2) - even though it has some common components with the DPAA, there's a certain amount of work to be done. In case someone has spare funds for this, please contact me directly :) Best regards, Marcin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPv3WKfEYz-2H-AvTB5=utCtP=TUEvgbaUYw9k7xFBib6KquyQ>