Date: Sat, 28 Mar 2020 22:15:20 +0000 From: greg@unrelenting.technology To: "=?utf-8?B?S2xhdXMgS8O8Y2hlbWFubg==?=" <maciphone2@googlemail.com>, "Mike Karels" <mike@karels.net>, freebsd-arm@freebsd.org Subject: Re: Switch to UEFI Re: CFT: alpha test of Ethernet driver for RPi4 Message-ID: <57d4ba4ef95eeaf382d2c0b2407e9dab@unrelenting.technology> In-Reply-To: <AA1CAD4B-2275-4988-A533-203D91808DE2@googlemail.com> References: <AA1CAD4B-2275-4988-A533-203D91808DE2@googlemail.com> <202003281622.02SGMcmi027728@mail.karels.net>
index | next in thread | previous in thread | raw e-mail
March 29, 2020 12:23 AM, "Klaus Küchemann via freebsd-arm" <freebsd-arm@freebsd.org> wrote: > I`m also working on pi4 a little while not ready… > I recommend to switch the whole RPI-thing to UEFI/ ACPI, J.McNeill is working on that , afaik… He's working on NetBSD a lot, but not on FreeBSD. > So next step I see is to implement ACPI-xhci-driver since FreeBSD-boot PANICS on xhci- That's not "implement a driver", that's "fix a bug" :) I was looking into this a month ago.. For some reason reading from the XHCI's memory space returns junk like 0xdead. And seems like nobody has seen that problem on NetBSD or Linux. I'll test this a bit more now. Once we get that working, and the Ethernet driver port is published, I could add ACPI attachment to the Ethernet driver. > The good news is that I first saw USB working in UEFI-boot...…the ethernet driver should then later > correspond or to be integrated into UEFI … nice to boot from a „Bios“ -style menu with a plugged > USB-keyboard... Yeah, eventually there's going to be a NetBSD-derived Ethernet driver in UEFI for network booting.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d4ba4ef95eeaf382d2c0b2407e9dab>