warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hipboi has joined #linux-rockchip
warpme has joined #linux-rockchip
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 264 seconds]
raster has quit [Quit: Gettin' stinky!]
hipboi has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 264 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
lorenzb has quit [Quit: Gateway shutdown]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 252 seconds]
<dTal>
Alright, it builds with cpufreq disabled. Probably don't want that for realtime anyway.
<CounterPillow>
You might want that to clock up the CPU from whatever bl31 sets lol
lorenzb has joined #linux-rockchip
punit has joined #linux-rockchip
hipboi has joined #linux-rockchip
stikonas has joined #linux-rockchip
hipboi has quit [Ping timeout: 264 seconds]
hipboi has joined #linux-rockchip
<dTal>
Well if so it can't be helped, at least not without tedious kernel hacking. My latency figures are *far* more consistent with CONFIG_PREEMPT and cpufreq disabled than CONFIG_PREEMPT_VOLUNTARY and cpufreq.
hipboi has quit [Ping timeout: 240 seconds]
warpme has joined #linux-rockchip
<macromorgan>
does anyone know if someone is working on the DSI controller for the RK3588? I'm looking at the datasheet with dread...
<CounterPillow>
Is it much different from the RK356x one?
<macromorgan>
yes, it appears to be Samsung IP for both the dphy and the controller itself. RK3399 notwithstanding past devices all appeared to use Designware IP
<macromorgan>
looks pretty damn distinct too from all the existing Exynos stuff
<macromorgan>
I can probably clean up the existing BSP drivers and mainline them, but the issue is supporting it... I doubt I have the necessary expertise to do that long-term for the mainline kernel.
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 252 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
crabbedhaloablut has quit []
crabbedhaloablut has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<CounterPillow>
You should probably ask somewhere that actually know what this is
<dTal>
Sorry. It's a version of OpenCV officially sanctioned by Luckfox and with Rockchip-specific code included. I thought it probable that someone else in here might have interacted with it.
<dTal>
As far as I know, it's the only prepackaged (read: lazy) way of getting data from the SC3336 camera using the rkisp libraries and other proprietary platform-specific imaging stuff.
stikonas has quit [Remote host closed the connection]
psydroid has quit [Read error: Connection reset by peer]
hipboi has quit [Ping timeout: 256 seconds]
stikonas has quit [Read error: Connection reset by peer]
stikonas has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
stikonas has quit [Read error: Connection reset by peer]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
leming has quit [Quit: bye!]
leming has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 260 seconds]
<dTal>
I figured it out. It's actually using GitHub Actions as a build system. It isn't buildable as-is, it's just a patchset for OpenCV and all the heavy lifting is done inside some hidden yaml file. Awful.