Date: Sun, 2 Jun 2024 11:50:55 -0700 From: Mark Millard <marklmi@yahoo.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: One less thing blocking UEFI+FDT support for HoneyComb Message-ID: <3EEB1061-50D7-4D02-8B2E-88F4D27AC8C2@yahoo.com> In-Reply-To: <33931s3s-oss6-90q2-8pr0-2809n6r83nos@yvfgf.mnoonqbm.arg> References: <DBBF4194-2D1D-41DE-95A6-4C77480D6185.ref@yahoo.com> <DBBF4194-2D1D-41DE-95A6-4C77480D6185@yahoo.com> <33931s3s-oss6-90q2-8pr0-2809n6r83nos@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 2, 2024, at 09:18, Bjoern A. Zeeb = <bzeeb-lists@lists.zabbadoz.net> wrote: > On Thu, 30 May 2024, Mark Millard wrote: >=20 >> (B) could well involve things not involving dpaa2 usage >> via FDT. >=20 > Is there's a problem with that please email dsl@ and bz@ and we can = have > a look. In general dpaa2 workes with both ACPI and FDT so... Unfortunately, even if someone committed draft kernel updates that might be needed (non-dpaa2) and someone else committed a draft sysutils/u-boot-honeycomb as well, my current personal context means that I'd not likely to be involved for many months, even in just testing such. Also, my use of EtherNet is very simple, not getting into things dpaa2 is designed to enable beyond basic 1Gbit/s EtherNet. So, even if I was testing, the range of dpaa2 configurations involved would be rather minimal compared to dpaa2's range of possibilities. Relative to FreeBSD generally, for now I'm in more of a monitoring/reading mode than anything else. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EEB1061-50D7-4D02-8B2E-88F4D27AC8C2>