<naoki>
how I should build, self build, or cross build...
warpme has joined #linux-rockchip
hipboi has joined #linux-rockchip
<naoki>
oh I remembered my current system(ubuntu server) uses dtb from u-boot...
raster has quit [Remote host closed the connection]
raster has joined #linux-rockchip
hipboi has quit [Quit: hipboi]
wens has quit [Ping timeout: 240 seconds]
wens has joined #linux-rockchip
hipboi has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hipboi has quit [Quit: hipboi]
warpme has joined #linux-rockchip
<dsimic>
Kwiboo: I'm sorry for the delay... going through the channel backlog
hipboi has joined #linux-rockchip
raster has joined #linux-rockchip
<dsimic>
Kwiboo: nice job, having the SoC variant printed in U-Boot will be very nice :)
naoki has quit [Quit: naoki]
franoosh has quit [Ping timeout: 246 seconds]
System_Error has joined #linux-rockchip
paulk has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
hipboi has quit [Quit: hipboi]
dsimic has quit [Ping timeout: 255 seconds]
dsimic has joined #linux-rockchip
franoosh has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mripard has quit [Quit: mripard]
mripard has joined #linux-rockchip
raster has joined #linux-rockchip
Stat_headcrabbed has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #linux-rockchip
hexdump0815 has joined #linux-rockchip
vagrantc has joined #linux-rockchip
<Kwiboo>
dsimic: thanks, it was nice to see more details about the SoC variant, not sure if we should print out the cpu-version or not, vendor kernel seem to use the cpu-version in very rare cases
<Kwiboo>
also maybe we should update the soc env var to match the detected soc
<dsimic>
IDK, I'd go with "it doesn't hurt to print a few more details" :)
<Kwiboo>
I am just not happy that printing out e.g. "SoC: RK3566T (cpu-version: 2)", the cpu-version part takes too much focus/space when the information is much less important, any suggestion on how to make it less verbose?
<dsimic>
hmm, maybe just "... (v2)"?
<dsimic>
and I agree that the verbose version steals the show
franoosh has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #linux-rockchip
alikates_ has joined #linux-rockchip
alikates_ is now known as alikates
franoosh has quit [Ping timeout: 252 seconds]
<Kwiboo>
dsimic: I will go with something like that, or possible just a letter, for most of my rk3588 the cpu-version seem to be v0 and that may seem strange to print out? using the letter for second position in the internal control code could possible work
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
<Kwiboo>
e.g. "RK3588 (A)" or "RK3588 (B)" vs "RK3588 (v0)" or "RK3588 (v1)"
<Kwiboo>
will test something out and send patches
franoosh has joined #linux-rockchip
stikonas has joined #linux-rockchip
raster has joined #linux-rockchip
naoki has joined #linux-rockchip
alikates has quit [Remote host closed the connection]
alikates has joined #linux-rockchip
<dsimic>
Kwiboo: to me, "... (v0)" and "... (v1)" look better
<dsimic>
heck, there are even many chip datasheets that are published as v0 :)
<dsimic>
actually, why not simply "... v0" and "... v1"? fewer characters, and less emphasis :)
<dsimic>
using an uppercase letter may also cause confusion with the letters that are part of the official SoC names
<dsimic>
so I think it's better not to use uppercase letters
raster has quit [Quit: Gettin' stinky!]
franoosh has quit [Remote host closed the connection]
<alikates>
Hello! Somebody here that has some experience with PX30/rk3326 DSI subsystem? I'm trying to make mainline linux work on one of these cheap retro gaming consoles, and I'm struggling to make the DSI panel work
<alikates>
It also doesn't help that the downstream ports lie in the DTB about the panel model, and just rely on the simple-panel initialization sequence -_-
<alikates>
The backlight shows some life, the panel driver also probes without issue and the fb device shows up. The only thing that comes to my mind is that the init sequence is incorrect, but thats just copy pasted from the downstream DTB...
<alikates>
AFAIU there's a video mux configured through the GRF, but I'm not completely sure about its relationship with this. Or even if it can be missing some config bits given that the DSI link in my current DTS is correct
sL1pKn07 has quit [Ping timeout: 255 seconds]
System_Error has quit [Remote host closed the connection]
Bitweasil- has joined #linux-rockchip
mripard has quit [Ping timeout: 245 seconds]
repk_ has quit [Ping timeout: 245 seconds]
Bitweasil has quit [Ping timeout: 245 seconds]
repk has joined #linux-rockchip
paulk has quit [Ping timeout: 245 seconds]
System_Error has joined #linux-rockchip
paulk has joined #linux-rockchip
paulk has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
sL1pKn07 has joined #linux-rockchip
sL1pKn07 has quit [Read error: Connection reset by peer]