04:46 <Armbian-Discord> <S​hoshee> @IgorPec Any documentation for making dtb with your generic ARM64 image?

05:01 <Armbian-Discord> <T​onymac32> ???

05:02 <Armbian-Discord> <T​onymac32> It would be added as a patch during build. So general use of the build system docs, then reading a lot about device trees

05:06 <Armbian-Discord> <S​hoshee> Any documentation for Generic ARM64 image installation on ARM64 supported devices?

05:07 <Armbian-Discord> <I​gorPec> is this your hobby project?

05:08 <Armbian-Discord> <S​hoshee> Yeah. I want to try your official ARM64 image.

05:08 <Armbian-Discord> <I​gorPec> then try and use google if it doesn't work

05:09 <Armbian-Discord> <S​hoshee> Sure. Thanks. Does it support the Apple M series chipset?

05:09 <Armbian-Discord> <I​gorPec> how should we know that??

05:09 <Armbian-Discord> <I​gorPec> ask Apple or try

05:10 <Armbian-Discord> <S​hoshee> Got it. 🫡

11:32 <Armbian-Discord> <M​anoftheSea> If you have a dtb

11:32 <Armbian-Discord> <M​anoftheSea> You should be getting dtb passed from bootloader

11:32 <Armbian-Discord> <M​anoftheSea> But as a workaround, you could add your own dtb to be passed to the kernel in the boot process

11:33 <Armbian-Discord> <M​anoftheSea> That makes it no longer a "generic" image

11:34 <Armbian-Discord> <M​anoftheSea> Er, from "platform firmware", which is the specific software for a board which initializes it and, optimally, knows what it is

11:59 <Armbian-Discord> <S​hoshee> Got it. Thanks.