Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 May 2020 00:49:35 +0000
From:      myfreeweb <greg@unrelenting.technology>
To:        =?ISO-8859-1?Q?Klaus_K=FCchemann?= <maciphone2@googlemail.com>, freebsd-arm@freebsd.org
Subject:   Re: rpi4-uefi.dev  Re: RaspberryPi 4B 8G model not boot
Message-ID:  <53680CD3-4FE9-42C9-A534-416A71263A08@unrelenting.technology>
In-Reply-To: <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com>
References:  <20200530.130909.120260481726933388.shigeru@os-hackers.jp> <D174CF68-09DC-48E0-A25A-321D2018908D@googlemail.com> <50DC156A-CA39-4809-85B7-02A5180DAB63@yahoo.com> <F3909CAB-488C-4315-ADFD-E769CD91C8B9@googlemail.com> <2DE76C92-8F4B-4658-94E4-FB7C7B7C6135@googlemail.com> <0AD80BEF-AA71-41F0-AD71-DF8516B790D9@yahoo.com> <67808784-29A6-4BC2-9B25-E31DE6DA862A@googlemail.com> <20C49D55-9940-422F-9699-4C56CFCF281B@unrelenting.technology> <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com>

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


On May 30, 2020 9:37:22 PM UTC, "Klaus K=C3=BCchemann" <maciphone2@googlem=
ail=2Ecom> wrote:
>=2E=2E O=2EK=2E, why do we do an acpi-split if there=E2=80=99s nothing el=
se than PNP0D10 in it ?=20
>NetBSD & OpenBSD don=E2=80=99t do  that file-split , afaik

They don't have driver inheritance=2E We do, so the usual pattern for devi=
ces available with both acpi and fdt is to have them inherit from a common =
driver that doesn't attach=2E

>> Looks like the problem is that the PCIe controller isn't getting initia=
lized,
>pcie isn`t exposed ( to the OS) in RPI4UEFI-dev , that=E2=80=99s what @An=
drejWarkentin told us =E2=80=A6
>And he told us what to do (in general, while not the easiest to understan=
d ;-)

Yep=2E Something has to initialize the actual controller though, that's wh=
at _INI does=2E So the OS runs the AML bytecode and initializes PCIe withou=
t even knowing PCIe exists=2E

I'll maybe look into this again soon=2E

>( attention : QWord )
>cutoff of an OpenBSD-file :
>xhci_acpi_parse_resources

That looks like just OpenBSD weirdness, the resources should be handled by=
 generic acpi code=2E

>to anticipate it: if we have solved this problem, we will probably end up=
 on vfs_mountroot because the uSD driver is not recognized under acpi, afai=
k

Screw uSD, I just put the OS on a USB stick and only the firmware on uSD=
=2E



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53680CD3-4FE9-42C9-A534-416A71263A08>