09:32 <tokyovigilante> kernel programming 101 question, where are the register read/write functions actually defined? eg which header should I import for writel()? And is there a good resource to find this sort of thing? Am using clangd for LSP but it seems to choke a bit on the kernel

10:42 <apritzel> #include <asm/io.h>

10:45 <apritzel> tokyovigilante: the writel() function itself is provided through asm-generic for arm64, which then calls __raw_writel from arch/arm64/include/asm/io.h

10:47 <apritzel> arm(32) handles everything in arch/arm/include/asm/io.h, as does riscv

13:46 <tokyovigilante> awesome, thanks apritzel

16:18 <maggio_> apritzel: How did you figure out boot0 for the Pine64 loaded u-boot from sector 38192

16:19 <maggio_> I'm trying to build firmware for the a133 using https://github.com/apritzel/pine64/blob/master/tools/boot0img.c

16:22 <apritzel> maggio_: oh, please don't go this way, this was really just because we didn't have DRAM init code early enough

16:23 <apritzel> maggio_: try to write *just* boot0 on an SD card, without having any other payload on there. I have seen some boot0 blobs going into FEL mode after DRAM init

16:23 <apritzel> which would allow you to upload U-Boot and a kernel

16:25 <apritzel> but be warned: bringing up firmware for a new SoC is not a walk in the park!

16:26 <apritzel> there is this, but no guarantees: https://github.com/apritzel/u-boot/commits/a133-WIP/

16:31 <maggio_> apritzel: thanks. will definitely take a look.

16:32 <maggio_> I guess getting boot0 to lood U-Boot from an SD card would not be at all trivial

16:34 <apritzel> maggio_: not really. Also AW changed and changes a lot in boot0 and their boot process compared to the A64, they already did with the H5 a year later, so we gave up on building on that