mmind00 changed the topic of #linux-rockchip to: Rockchip development discussion | public log at https://libera.irclog.whitequark.org/linux-rockchip
urja has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
kevery1 is now known as kevery
System_Error has quit [Ping timeout: 260 seconds]
hexdump0815 has quit [Ping timeout: 255 seconds]
hexdump0815 has joined #linux-rockchip
ungeskriptet has quit [Ping timeout: 276 seconds]
ungeskriptet has joined #linux-rockchip
crabbedhaloablut has quit []
crabbedhaloablut has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
<naoki> after making 40+ patches for ROCK 5B, I understand ROCK 5B and 5T(5B++) is very similar
<naoki> I think I'm doing something wrong...
Stat_headcrabbed has joined #linux-rockchip
<mriesch> naoki: nevertheless a valuable insight. better late than never :-)
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery has joined #linux-rockchip
kevery1 has quit [Ping timeout: 245 seconds]
franoosh has joined #linux-rockchip
franoosh has quit [Changing host]
franoosh has joined #linux-rockchip
warpme has joined #linux-rockchip
raster has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
franoosh has quit [Changing host]
franoosh has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 245 seconds]
kevery1 is now known as kevery
<mripard> Hi, is there any reason to use Collabora's ATF fork for the RK3588 still, or is the upstream support in good shape now?
HeyMeco has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
HeyMeco has quit [Quit: Client closed]
<qschulz> sre: ^ maybe a question for you?
<mmind00> qschulz: I think the scmi for the cpu clocks was merged?
raster has joined #linux-rockchip
<qschulz> there's crypto upstream as well, so not sure what collabora had in their own fork
<mmind00> qschulz: nice ... then I guess all the main functionality should be there
<mmind00> mripard: ^^
<mripard> yeah, that's what started the question, I saw that the support looked somewhat there, but the collabora doc seems updated as well, so I wasn't sure :)
clarity has quit [Ping timeout: 252 seconds]
<diederik> you may want to verify whether it actually works ...
<diederik> ref https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/31265 and the discussion has since been continued off-gerrit
<mmind00> diederik: that's rk3568 though
<diederik> correct, but that should('ve been) based upon the rk3588 implementation
<mmind00> diederik: The rk3568 and rk3588 stuff were done by different Rockchip devs
<diederik> yes and hopefully the rk3588 does work properly. Still, I think it's better to verify that then to assume
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<mmind00> in any case, the collabora rk3588 TF-A repo does not seem to include any non-mainline commits in their rk3588 branch
<diederik> My most recent test report for rk3568: https://paste.sr.ht/~diederik/7b9b2aa4bddef0669b7d18183f0ccc19e3d2826f
<diederik> oh yeah, I definitely think you should try with the upstream stuff
<diederik> "all the main functionality should be there" = completely true, but that doesn't automatically mean everything works flawlessly
raster has quit [Quit: Gettin' stinky!]
raster has joined #linux-rockchip
raster has quit [Client Quit]
raster has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
clarity has joined #linux-rockchip
raster has joined #linux-rockchip
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
<naoki> I made 30+ patches to update rock-5b.dts... I'm tired...
warpme has joined #linux-rockchip
<naoki> making rock-5b-plus.dts should be more creative work...
<naoki> btw I'm confusing about u2phy and schematic relation
warpme has quit [Client Quit]
warpme has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
HeyMeco has joined #linux-rockchip
<HeyMeco> naoki are you working on rock5b plus device tree? I wanted to do that last week but I got sick and now am caught up with other work '=D
HeyMeco has quit [Client Quit]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
raster has quit [Quit: Gettin' stinky!]
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
raster has joined #linux-rockchip
dsimic has quit [Ping timeout: 248 seconds]
warpme has joined #linux-rockchip
dsimic has joined #linux-rockchip
warpme has quit [Client Quit]
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
naoki has quit [Quit: naoki]
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
warpme has joined #linux-rockchip
System_Error has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
mripard has quit [Quit: WeeChat 4.4.2]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
<qschulz> a3f: does Barebox fixup the kernel DT to add where the bootrom loaded barebox from?
<qschulz> I want to add something like that for U-Boot and I think it'd make sense to reuse the same fdt prop since it's nothing bootloader specific
<a3f> qschulz, yes, /chosen/bootsource contains the full path to the boot device node
<qschulz> a3f: is this part of any standard yet?
<a3f> nope, afaik no one ever submitted a binding for it
<qschulz> Doesn't seem to be in the devicetree-specification for the /chosen node yet
<a3f> your chance ;)
<qschulz> a3f: just to be sure, this is storing the storage medium used by the BROM to load Barebox, not which storage medium is used to load the kernel for example?
<qschulz> bootsource could mean both
<a3f> qschulz, the BootROM's bootsource. Where the kernel came from can usually be inferred from the rootfs
<qschulz> a3f: that's really just a guess ;)
<qschulz> a3f: ok, thanks for the info
<qschulz> I guess we should try to put this in the spec then
<qschulz> hopefully without a rename :) but that isn't up to me
<a3f> On a similar note, barebox also fixes up /chosen/reset-source to indicate if it was a watchdog reset for example or a POR
<a3f> I think a rename is acceptable if that's what it takes for it to get upstream. We can always fix up both strings for a transitory period and then hide one behind an option
<qschulz> ok, we also are attempting at detecting the reset cause in U-Boot as well
<qschulz> but we only print the reason atm
<qschulz> will try to remember for next week :)
<qschulz> have a nice week-end everybody
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
Hypfer6 has quit [Quit: The Lounge - https://thelounge.github.io]
Hypfer6 has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
stikonas has joined #linux-rockchip
raster has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
Stat_headcrabbed has quit [Remote host closed the connection]
paulk has quit [Ping timeout: 276 seconds]
naoki has joined #linux-rockchip
paulk has joined #linux-rockchip
paulk has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
vagrantc has joined #linux-rockchip
crabbedhaloablut has quit []
crabbedhaloablut has joined #linux-rockchip