<qschulz>
not merged yet, but should be in time for 2024.10
<qschulz>
you could probably rebase on top of 2024.07 in our own tree
<qschulz>
should be released in about 2-3 weeks
<qschulz>
it's possible not everything will work though, for example we discovered recently that with upstream U-Boot you couldn't get DSI working on downstream or upstream kernel
<qschulz>
it was patched, but maybe something similar isn't working for HDMI as well
mort has quit [Read error: Connection reset by peer]
mort has joined #linux-rockchip
Livio has quit [Ping timeout: 252 seconds]
<mort>
huh my IRC client crashed/restarted, weird
<mort>
anyway, AFAIK that HDMI patch set is not merged yet so there is no upstream HDMI support. I want to try to get that working so that I can try the panthor GPU drivers, but first I think I wanna try to get Rockchip's official stuff working
Daanct12 has joined #linux-rockchip
<qschulz>
mort: what I meant to say is that with Rockchip's kernel but upstream U-Boot we didn't have DSI working
<qschulz>
until we patched U-Boot
<qschulz>
and I'm saying that MAYBE something similar could happen for HDMI
<mort>
aha
<mort>
though apparently upstream u-boot doesn't even generate.a uboot.img so I still have some figuring out to do
<qschulz>
so, try and see for yourself but there may be a bit more work than just using vanilla upstream U-Boot for this to work
<mort>
oh, I thought you meant instructions for getting the yocto recipe to generate uboot.img
<qschulz>
mort: in short, you should be able to write u-boot-rockchip.bin to offset 64 (32KB) on your MMC
<qschulz>
there seems to be a chapter for generating uboot.img
<qschulz>
but I have never used those, u-boot-rockchip.bin and u-boot-rockchip-spi.bin for our boards
<mort>
and trust.img interestingly
<mort>
anyway those instructions naturally don't tell you how to get the yocto recipe to get u-boot to generate a uboot.img or u-boot-rockchip.bin or u-boot-rockchip-spi.bin or anything else
<qschulz>
mort: start small, build stuff manually, flash at the proper offset, then integrate it into Yocto
<mort>
so I tried to add DEPENDS += "u-boot" to my image recipe, I have never seen other image recipes do this and I assumed that PREFERRED_PROVIDER_virtual/bootloader="u-boot" would take care of that but apparently not. Regardless, compiling u-boot with the evb-rk3588 defconfig complains that a TPL binary is missing... I feel it's easier to "just" use
<mort>
u-boot-rockchip
<naoki>
define BL31 and ROCKCHIP_TPL, written in doc
<mort>
yeah but that requires modifying the u-boot recipe and I really really don't wanna have to deal with that right now
<qschulz>
mort: all I can tell you is that Rockchip's U-Boot is REALLY painful to work with
<qschulz>
and considering the current support in upstream U-Boot for RK3588, I think it's really worth it to spend a bit of time to get it to work on your board
<qschulz>
especially since there are already patches available to support it
<mort>
my experience is that the current support in upstream anything for rk3588 is pretty terrible
<qschulz>
mort: have you tested upstream U-Boot yet?
<mort>
only insofar as the aforementioned build errors due to the missing TPL binary
<qschulz>
mort: you didn't follow the instructions, cannot complain that it doesn't work ;)
<mort>
qschulz: there are no instructions for the u-boot recipe, and if they were it would be: set PREFERRED_PROVIDER_virtual/bootloader to "u-boot" and maybe add u-boot to DEPENDS
<qschulz>
mort: 1) I gave you the link to the u-boot docs that explain how to compile it manually
<qschulz>
2) I told you to start small and ignore Yocto for now
<qschulz>
3) I have you a link to how this is done in community maintained meta-rockchip
<qschulz>
not wanting to use upstream is fine, but don't say it doesn't work when you haven't even used it
<naoki>
btw, TF-A master want aarch64-none-eabi-gcc, I don't know easy way to prepare it on ubuntu 24.04 userland :( I don't want to make toolchains from source...
Livio has quit [Ping timeout: 268 seconds]
<naoki>
LLVM can be used for TF-A, but I got error, I gave up to try TF-A master branch (lts branch is fine)
<naoki>
should be fine. not tried yet
<naoki>
plat/rockchip/rk3399/drivers/dram/dram_spec_timing.c:781:11: error: explicitly assigning value of variable of type 'uint32_t' (aka 'unsigned int') to itself [-Werror,-Wself-assign]
<naoki>
781 | twr_tmp = twr_tmp;
<naoki>
| ~~~~~~~ ^ ~~~~~~~
<naoki>
lol
<mort>
there is very little in this world I hate more than -Werror
<mort>
naoki: but you may be able to change build options to disable -Werror somehow