mmind00 changed the topic of #linux-rockchip to: Rockchip development discussion | public log at https://libera.irclog.whitequark.org/linux-rockchip
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #linux-rockchip
qschulz has quit [Remote host closed the connection]
qschulz has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
hanetzer has quit [Ping timeout: 252 seconds]
hanetzer has joined #linux-rockchip
hexdump0815 has quit [Ping timeout: 260 seconds]
hexdump0815 has joined #linux-rockchip
naoki has quit [Quit: naoki]
naoki1 has joined #linux-rockchip
naoki1 is now known as naoki
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
cbeznea has joined #linux-rockchip
warpme has joined #linux-rockchip
raster has joined #linux-rockchip
ldevulder has joined #linux-rockchip
ldevulder has quit [Ping timeout: 260 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ldevulder has joined #linux-rockchip
warpme has joined #linux-rockchip
hanetzer has quit [Ping timeout: 260 seconds]
hanetzer has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
naoki has quit [Remote host closed the connection]
warpme has joined #linux-rockchip
<detlevc> warpme: for what you see in Kodi, I'm wondering if you are seeing the colmv part of the buffer shown on top of the frame. Technically, the driver allocates a bigger buffer for each frame to store those colmv (because we need one associated to each frame). So the userspace has the responsability to only use the frame data (bytesperline * height),
<detlevc> could that be the issue here ?
<detlevc> I couldn't reproduce with kodi yet, does it have its own v4l2-requests implementation ?
<warpme> detlevc : i don't think so. Why: 1. i have 4 other soc families (amlogic, allwinner, broadcom and earlier rockchip) all works perfectly fine. rkvdec1 (33xx) and rkvdec2 (3588) also works ok. issue seems to be only with rkvdec3. 2. on rkvdec3 sometmes i have perfect playback. it happens randomly but happens....
<warpme> overal 35+ diff bards works ok....
<detlevc> warpme: rkvdec3 is rk3576, right ?
<warpme> re kodi v4l2_req implementation: both player i'm using are based on the sem ver of ffmpeg (7.1) with the same v4l2_req implementation. so maybe v4l2_req kodi/mytht uses is simply not compatible with rkvdec3? if - why sometimes (once per 15-20 playbacks) i have perfect playback on rkvdec3?
<warpme> yes. ndufresne uses this notation so i borrowed form him :-p
<warpme>
<detlevc> it shouldn't be incompatible, plus it shares most setup code with rk3399, so it is probably a bug or a bad assumption somewhere. I'll try to reproduce later and then trace it
<warpme> this will be qll. if i can help in any way - would love do so....
<detlevc> what is qll ? :p
<warpme> oh: i must say collabora is white knight in rk ecosystem for me. without you, crisitian, derek, sebastian poor souls like me will probably abandon masohistic world of linux on low end embedded socs
<warpme> qll (for me) is to have hw assisted hd/4k tv playback on board costing 1/5 of x86 counterpart and being 10x smaller and running full foss based diskless distributed media center (mythv). or on the same board running https://endeavouros.com
<warpme> i'm fan of archlinux and endeavouros 7 diff DE to play with on 4c 4G ram 25Eur devices
System_Error has quit [Remote host closed the connection]
<diederik> detlevc: I don't know about kodi in general, but for LibreELEC, there's https://github.com/LibreELEC/LibreELEC.tv/tree/master/packages/multimedia/ffmpeg/patches/v4l2-request
System_Error has joined #linux-rockchip
dsimic has quit [Ping timeout: 252 seconds]
dsimic has joined #linux-rockchip
vagrantc has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ldevulder has quit [Ping timeout: 276 seconds]
<detlevc> diederik: I already use a patched version of ffmpeg, do I need a specific version of kodi to have v4l2request support ? I have debian's version 21.2
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
cbeznea has quit [Ping timeout: 252 seconds]
stikonas has joined #linux-rockchip
<CounterPillow> robmur01: Out of curiosity, as the resident member of the A-team here, does Rockchip's interconnect probe hardware on RK3588/RK3399/RK3326/probably more look vaguely familiar to you? I saw they switched to CCI-500 on RK3576 which got me curious, but neither arm-ccn nor arm-cci seem to fit the bill as far as the probe design goes for earlier chips.
<CounterPillow> Just flipping through PDFs and code files in a panic at the moment to make sure I didn't just begin writing a driver that already exists. Some hardware particulars: 4 16-bit counters per probe, can be chained together to 2 32-bit counters. 8 probes in total, +4 DSU probes which need to be all summed together. References to an "ObsTx observation output" that does not seem mentioned anywhere else, which makes me think vestigial
<CounterPillow> leftover from IP configuration.
<diederik> detlevc: AFAIK they've had that patch set for a while. But other then using it with LibreELEC (on Rock64), I've not done anything with kodi directly
<diederik> I don't think Debian's version of kodi has/uses the LE patchset though.
<diederik> detlevc: I deliberately make a distinction between kodi and LibreELEC; I think only the latter has the v4l2-request patch set
<diederik> And afaict the Debian package is 'normal' kodi
valpackett has quit [Ping timeout: 244 seconds]
vagrantc has quit [Quit: leaving]
valpackett has joined #linux-rockchip