00:48 <chewitt> hexdump0815 .. but, but, but, .. Odroid C2 (which has 'special' boot FIPs) can be installed to an eMMC module with MBR partition table

00:58 <chewitt> the last two commits are picked from forks of afaerber's meson-tools repo https://github.com/chewitt/meson-tools/commits/fixes

00:59 <chewitt> the "Add the ability to embed MBR in the bootloader" commit is perhaps the key

00:59 <chewitt> I haven't managed to wrap my head around using those tools

01:00 <chewitt> (and can't read code, which is a liability for understanding what that change does)

16:19 <tortoise> I'm interested in working on the VPU encoder support (venc?) for the amlogic mainline. I'd like to start with the h264 encoder, that is if thats realistic and not too deep of waters. So I have some linux kernel experience as well as reversing but this would be a whole new world for me in many respects. I've been working my way through Neil's talks as well as the Paul Kocialkowski's of bootlin's rockchip encoder work. I

16:19 <tortoise> have some radxa zero boards that I can develop on. But now I'm trying to figure out how to even get started. I've followed a link to openlinux.amlogic.com and I see the older kernels, but you need to login to download them and the registration button doesn't do anything it. Is there any bandwidth in this community to support an eager volunteer in ramping up?

18:10 <kenny> ty hexdump0815 & chewitt. I plan to try building something to run on the emmc this weekend. I'm wondering, what's the deal with '446'. Why that value and what lives between that and 512?

18:21 <Consolatis> narmstrong and everybody else working on amlogic parts of the kernel and u-boot: just wanted to thank you all for your work.

18:21 <Consolatis> I am using an Odroid C4 as daily driver for dev work + browsing / YouTube and the C2 before that. Current Uptime is 75 days with daily use and its rock stable.

19:02 <narmstrong> Consolatis: thanks, you’re welcome !

19:03 <narmstrong> tortoise: you can start looking at the kernel Hardkernel & module provides to start up

19:03 <narmstrong> tortoise: we will do our best to answer your questions here or on the mailing list

19:04 <narmstrong> kenny: there is an important mbr byte at the end of the first sector

22:15 <syscall> hello, is anyone aware of issues impacting sm1/odroid-c4 booting recent kernels? seeing a boot hang on 5.16.10 unless I use a dtb from older release

22:20 <syscall> primary differences appear to be related to addition of gpu, sound controller, and watchdog- still trying to identify the exact problem

22:22 <steev> where is it hanging at?

22:53 <syscall> steev: it allocates fb0 with simple-framebuffer and then no additional information- I can't seem to get any debugging info out of this kernel build

22:53 <steev> serial console?

22:53 <syscall> steev: with the older device tree it gets past that and the next step is ALSA soundcard detection

22:54 <syscall> steev: yes, though I attached a display (for the first time ever!) and just saw four penguins and a non-blinking cursor

22:59 <syscall> going to try adding an overlay to disable sound and gpu to see if that will let me operate like normal, but willing to help test other things if this is a known issue affecting other people

23:49 <hexdump0815> kenny: between 446 and 512 bytes is the mbr partition table with its 4 primare partitions and that conflicts a bit with the boot block on gxbb, which is written from the beginning of the disk - most others start after 512 byte or later