Hi Mark,
On Wed, 08 Jan 2025 14:08:55 +0100,
Mark Kettenis <mark.kette...@xs4all.nl> wrote:
> > Have I miss something? Maybe here some magic that allows to discover
> > everything on FDT tree?
> 
> The ACPI information on these machines is barely usable.  ACPI is just
> not a very good match for these SoC based systems.  Microsoft "solved"
> that problem with PEPs, which are basically system-specific drivers
> that encode a lot of information about the SoC and how it's actually
> wired up in the machine in the driver itself.  Basically it means you
> have to write a customized driver for each system...  And the
> interfaces between PEP and ACPI are largely undocumented.
> 
> So the way we support these systems on OpenBSD is that we require a
> proper FDT for the machine.  These FDTs are made available through the
> arm64-qcom-dtb "firmware" package that is built from the
> sysutils/firmware/arm64-qcom-dtb port.  The way this is works is that
> we have implemented some minimal ACPI support that is good enough to
> run the installer.  The installer will download the firmware package
> and installs it.  Upon the next boot, the bootloader will find the FDT
> and load it before passing control to the kernel.
> 
> So in order to properly support your system you need to:
> 
> 1. Create an FDT for your system.  I don't think this particular
>    system is supported by Linux yet, but it might be worth asking on
>    the #aarch64-laptops channel on the OFTC IRC server (irc.oftc.net)
>    if someone is working on it.  If not, maybe ask mglocker@ for some
>    guidance; he created an FDT for his Samsung Galaxy Book4 Edge.
> 
> 2. Add the FDT to the sysutils/firmware/arm64-qcom-dtb package.
> 
> 3. Add an entry for your machine to the mapping table in
>    sys/arch/arm64/stand/efiboot/efiboot.c such that the FDT gets
>    loaded automatically.
> 

Thanks for explanation, indeed I've missed something.

I've jsut asked, no, here no one on that channel who working ok FDT.

Marcus, may I kindly ask you about some guidance how to build FDT from
scratch without any documentation (I can't find anything)? :)

-- 
wbr, Kirill

Reply via email to