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>
next in thread | previous in thread | raw e-mail | index | archive | help
March 29, 2020 12:23 AM, "Klaus K=C3=BCchemann via freebsd-arm" <freebsd-= arm@freebsd.org> wrote:=0A=0A> I`m also working on pi4 a little while not= ready=E2=80=A6=0A> I recommend to switch the whole RPI-thing to UEFI/ AC= PI, J.McNeill is working on that , afaik=E2=80=A6=0A=0AHe's working on Ne= tBSD a lot, but not on FreeBSD.=0A=0A> So next step I see is to implement= ACPI-xhci-driver since FreeBSD-boot PANICS on xhci-=0A=0AThat's not "imp= lement a driver", that's "fix a bug" :)=0AI was looking into this a month= ago..=0AFor some reason reading from the XHCI's memory space returns jun= k like 0xdead.=0AAnd seems like nobody has seen that problem on NetBSD or= Linux.=0AI'll test this a bit more now.=0A=0AOnce we get that working, a= nd the Ethernet driver port is published, I could add ACPI attachment to = the Ethernet driver.=0A=0A> The good news is that I first saw USB working= in UEFI-boot...=E2=80=A6the ethernet driver should then later=0A> corres= pond or to be integrated into UEFI =E2=80=A6 nice to boot from a =E2=80= =9EBios=E2=80=9C -style menu with a plugged=0A> USB-keyboard...=0A=0AYeah= , eventually there's going to be a NetBSD-derived Ethernet driver in UEFI= for network booting.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d4ba4ef95eeaf382d2c0b2407e9dab>