Switch to UEFI Re: CFT: alpha test of Ethernet driver for RPi4

[Klaus Küchemann]

> Am 28.03.2020 um 23:39 schrieb greg at unrelenting.technology:
> 
> 
> What allwinner?
> How did you find anything allwinner-related in ACPI code, when AFAIK no Allwinner SoC ever had ACPI tables written for it?
> 
> I'm talking about generic XHCI.

Sorry, I always mix up Allwinner with Marvell,
where you changed some things in generic_xhci_fdt. …
Mo matter, what I wanted to say is that there perhaps could be some need to add things
for the bcm-soc what is called ACPi-glue by jmcneill in his sources…
`hope you are right that it `ll be only a simple bugfix for you to get the right IRQ setup in generic_xhci.c …


> Am 28.03.2020 um 23:27 schrieb Mike Karels <mike at karels.net>:
> 
> 
> I’m not ready to put the source out in public, as the copyright notice is not yet approved.  I’ll put it in phabricator when it’s ready.
> 
> About UEFI: I don’t know what’s involved, but half of the driver interfaces with the rest of the network stack, and I don’t see how using UEFI simplifies any of that.
> 
> 		Mike

O.K., seems I misunderstood your 'alpha test‘- offer…
I thought you wanted us to test/review your code before you put it to phabricator.

Well, jmcneill, where you derived the genet-driver-sources from, has already 
integrated the driver  in UEFI, while it is not yet integrated in rpi4-uefi upstream, afaik.
You can dual-boot in UEFI from dt(hangs at gpioregulator at the moment) or ACPI(hangs unrelenting at greg`s irq-code at the the moment[.. just kidding] .
They are working on netboot at the moment .. 
I really suggest to track the UEFI - devs to understand what’s going on there.. 
it could be the right way to finally get this damned board under control..


Regards

Klaus