Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Mar 2020 11:17:24 -0500
From:      "Mike Karels" <mike@karels.net>
To:        "Klaus =?utf-8?q?K=C3=BCchemann?=" <maciphone2@googlemail.com>
Cc:        "Greg V" <greg@unrelenting.technology>, freebsd-arm@freebsd.org
Subject:   Re: Switch to UEFI Re: CFT: alpha test of Ethernet driver for RPi4
Message-ID:  <C537E77F-91AE-486B-9D92-E61FA6FD6E76@karels.net>
In-Reply-To: <C07E205F-410E-49C3-B98A-08769D295A39@googlemail.com>
References:  <964BBCA2-5EE1-4673-966E-63D37FEDB4EA@googlemail.com> <AA1CAD4B-2275-4988-A533-203D91808DE2@googlemail.com> <202003281622.02SGMcmi027728@mail.karels.net> <57d4ba4ef95eeaf382d2c0b2407e9dab@unrelenting.technology> <3d84dbd6acea80b04bee712b59661a86@unrelenting.technology> <C07E205F-410E-49C3-B98A-08769D295A39@googlemail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 29 Mar 2020, at 9:53, Klaus K=C3=BCchemann wrote:

>> Am 28.03.2020 um 23:39 schrieb greg@unrelenting.technology:
>>
>>
>> What allwinner?
>> How did you find anything allwinner-related in ACPI code, when AFAIK=20
>> 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. =E2=80=A6
> Mo matter, what I wanted to say is that there perhaps could be some=20
> need to add things
> for the bcm-soc what is called ACPi-glue by jmcneill in his sources=E2=80=
=A6
> `hope you are right that it `ll be only a simple bugfix for you to get=20
> the right IRQ setup in generic_xhci.c =E2=80=A6
>
>
>> Am 28.03.2020 um 23:27 schrieb Mike Karels <mike@karels.net>:
>>
>>
>> I=E2=80=99m not ready to put the source out in public, as the copyrigh=
t=20
>> notice is not yet approved.  I=E2=80=99ll put it in phabricator when i=
t=E2=80=99s=20
>> ready.
>>
>> About UEFI: I don=E2=80=99t know what=E2=80=99s involved, but half of =
the driver=20
>> interfaces with the rest of the network stack, and I don=E2=80=99t see=
 how=20
>> using UEFI simplifies any of that.
>>
>> 		Mike
>
> O.K., seems I misunderstood your 'alpha test=E2=80=98- offer=E2=80=A6
> I thought you wanted us to test/review your code before you put it to=20
> phabricator.

I=E2=80=99m ready to provide source to individual testers, but not to pub=
lish=20
it yet.  For anyone that wants to try it, I can provide source and maybe=20
a kernel; I=E2=80=99m not set up to do full images.  I=E2=80=99ll also no=
te that=20
I=E2=80=99m testing using a kernel that is not recent, because it boots w=
ith=20
my current u-boot, but I suspect it will work fine with a recent kernel.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C537E77F-91AE-486B-9D92-E61FA6FD6E76>