ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
psydroid3 has joined #linux-rockchip
<Kwiboo>
chewitt, diederik: no problem, I have not had time to test it, but I expect it should help fix the issue, ffmpeg will always try to use NV12 format without the get_image_fmt ops, and for the 10-bit case NV15 must be used
<Ermine>
seems like people love nv12
<diederik>
Kwiboo: with ``[ffmpeg] V4L2RequestContext: Failed to set 1 control(s): Invalid argument (22)`` it was correctly detected as 10-bit and NV15 was used ... only it resulted in a completely blue screen (which is potentially different from the issue I reported to LE)
raster has joined #linux-rockchip
psydroid3 has quit [Ping timeout: 248 seconds]
ungeskriptet has quit [Remote host closed the connection]
<Kwiboo>
diederik: most likely that is a different issue, the nv15 pixel format is a very niche format, so unless all parts in the display pipeline fully support it, I would not expect it to be rendered correctly, especially when the video frames is imported into and rendered by the GPU
<diederik>
Yeah, one thing I recently found out is that sway defaults to 8-bit rendering and you need to have ``output * render_bit_depth 10`` in your sway config (learned that via https://man.archlinux.org/man/sway-output.5.en)
<diederik>
and then there could indeed be other parts of the pipeline which may also need to be made aware of 10-bit stuff
psydroid3 has joined #linux-rockchip
stikonas has joined #linux-rockchip
<naoki>
Kwiboo: By the way, thanks to U-Boot's generic-rk3xxx_defconfig I can work on the OpenWrt port before finishing the U-Boot port. :) https://github.com/openwrt/openwrt/pull/19867
psydroid3 has quit [Ping timeout: 245 seconds]
stikonas has quit [Quit: Konversation terminated!]
pastaonirc has quit [Ping timeout: 258 seconds]
pastaonirc has joined #linux-rockchip
franoosh has joined #linux-rockchip
<Kwiboo>
naoki: great!, something like that was main purpose for the generic targets, prior to adding the generic targets I typically used the evb targets for any board without full upstream support, and tha could cause other strange issues if the evb is a fully described in DT
<Kwiboo>
for network targets I would also try how the boards would behave with a proper u-boot target, some init for network may happen in u-boot if a DT for the actuall board is used, the generic targets avoid anything beside bare minimum to boot