02:28 <maku> Hey there, I'm trying to compile the latest mainline kernel on my AMLogic based device (Spotify CarThing). Because of the uboot protection I can't use the `bootm` command though, so I put the Image and DTB on a fat32 partition, and load those using fatload command and then try to boot the image using `booti`, but unfortunately I'm getting "Could not find a valid device tree" error on the uboot console

02:28 <maku> Anyone have any clue what I might be doing wrong/what I should try next?

02:32 <maku> It looks like loading kernel image overrides the ftd and vice verse

02:39 <maku> (Chip is S905D2 if that matters)

03:07 <steev> are you able to pass kernel command line arguments? you should be able to pass dtb= to the kernel that way

03:11 <vagrantc> use different offsets?

03:12 <vagrantc> e.g. ones that don't overwrite the .dtb loaded into ram... upstream u-boot usually has fdt_addr_r below the kernel, since it is much less likely to grow significantly in size (with still a significant buffer)

03:27 <maku> yeah, i do load DTB at 0x01000000 and the kernel at 0x01080000

03:28 <maku> which means I have 512kb for DTB which should be enough

04:05 <maku> Just to make sure - when the howto mentions "mainline kernel" does it mean I can simply get the latest release from kernel.org and use the defconfig from there?

05:16 <chewitt> maku: what kind of u-boot "protection" is present?

05:38 <maku> I assume some sort of secure boot signature check

05:39 <maku> I managed to boot 6.1 kernel now but obviously my DTS from 4.19 does not work anymore

07:21 <narmstrong> maku: the vendor dts can’t work on mainline kernel at all

07:22 <maku> So I assume I'll have to write a DTS from scratch

07:24 <narmstrong> maku: you can take a basic s905d2 dts from upstream like https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-g12a-u200.dts

07:26 <maku> I've tried that, the kernel immediately crashes on me

07:26 <maku> https://gist.github.com/worst-computer-user/8fff6161608f234aa95a3b266dcad761

07:27 <narmstrong> Change the memory node length, afaik the thing has a little ddr chip

07:31 <maku> That helped, thank you!

07:31 <maku> Now to figure out why I have no mmc

08:24 <maku> hmmm, I only get 2 mmc block devices that are 2mb big each

09:32 <maku> Hah, at least managed to get the USB host mode working

09:32 <maku> Which is what I wanted to do in the first place

09:33 <maku> Problem is that one step forward cost me losing proper access to MMC partitions (but I guess I can just hardcode offsets of uboot partitions and mount them as loop devices), LCD driver, and basically everything else

10:12 <narmstrong> maku: why do you want to access the eMMC ?

10:12 <narmstrong> you can leave it alone

10:12 <maku> I want to mount the partitions there, since that's where the rootfs is

10:14 <maku> but either way, i don't think this is the way to do what I want to do, looks like the mainline kernel is missing lots of amlogic drivers that I need and unforunately I lack the skill to port those over

10:19 <narmstrong> ?

10:19 <narmstrong> maku: the vendor rootf won't work with mainline

10:20 <narmstrong> maku: what driver are you missing ?

10:20 <narmstrong> maku: the LCD support is not upstream but there's a patchset for that

10:20 <narmstrong> maku: in the meantime you can locate the framebuffer set by u-boot and use simple-framebuffer to update it from linux

10:21 <maku> narmstrong: I know that the vendor rootfs won't work with mainline, but I need to put my rootfs somewhere, hence why I would like to be able to access the system_a/system_b partitions to store that

10:22 <maku> narmstrong: I would love to learn more about that patchset, and perhaps how to configure the DTS to use the uboot framebuffer as simple-framebuffer

10:22 <maku> narmstrong: if it's not clear from the above - i have absolutely no idea what i'm doing, so any help is very appreciated

10:23 <narmstrong> maku: enabling the DSI panel needs some skills, so it's not the simplest