<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>
***: montjoie has quit IRC (Ping timeout: 480 seconds)
<br> BrianG61UK_ has joined #linux-media
<br> NiksDev2 has joined #linux-media
<br> NiksDev has quit IRC (Ping timeout: 480 seconds)
<br> jm_h has joined #linux-media
<br> lucaceresoli has joined #linux-media
<br> miqztee has joined #linux-media
<br> ao2 has joined #linux-media
<br> camus has quit IRC (Remote host closed the connection)
<br> camus has joined #linux-media
<br> GBenji has joined #linux-media
<br> svarbanov has joined #linux-media
<br> ao2 has quit IRC (Quit: Leaving)
<br> NiksDev2 has quit IRC (Remote host closed the connection)
<br> NiksDev2 has joined #linux-media
<br> djrscally has joined #linux-media
<br> miqztee has quit IRC (Ping timeout: 480 seconds)
<br> camus1 has joined #linux-media
<br> camus has quit IRC (Ping timeout: 480 seconds)
<br> mort_ has joined #linux-media
mort_: hey, for whatever reason, I'm getting an "Unable to parse link: Operation not permitted (1)" error when trying to run a `media-ctl -d /dev/media0 -l ...` command. I'm running the command as root, and /dev/media0 exists. Does anyone have any suspicions about what might be wrong, or can I enable debug prints somehow?
<br> Nothing is printed to dmesg even though I wrote 0x1f to all the dev_debug files I could find in /sys/class/video4linux
<br> --print-dot prints https://p.mort.coffee/WbI
***: camus has joined #linux-media
<br> camus1 has quit IRC (Remote host closed the connection)
<br> hverkuil has quit IRC (Quit: ZNC 1.8.2+deb2+b1 - https://znc.in)
<br> hverkuil has joined #linux-media
<br> hverkuil has quit IRC ()
<br> hverkuil has joined #linux-media
<br> NiksDev2 has quit IRC (Remote host closed the connection)
<br> NiksDev2 has joined #linux-media
<br> svarbanov has quit IRC (Ping timeout: 480 seconds)
<br> svarbanov has joined #linux-media
<br> svarbanov has quit IRC (Ping timeout: 480 seconds)
<br> svarbanov has joined #linux-media
<br> svarbanov has quit IRC (Ping timeout: 480 seconds)
<br> BrianG61UK has quit IRC (Read error: Connection reset by peer)
<br> svarbanov has joined #linux-media
kbingham: hverkuil, Hi!, I'd like to properly test that vb2 fix you sent, and I recall you said there was a control in vivid to potenitally recreate the issue - I can't find that reference though, was I dreaming?
hverkuil: <u>kbingham</u>: what vb2 fix? I've been working on other things and this fell out of my brain-cache...
kbingham: hverkuil, Ah, the title of the patch is "vb2 fix" ;-)
<br> It was to do with a qbuf failing
<br> or more precisely ...
hverkuil: ah yes.
kbingham: If the stream fails to start, it doesn't return a buffer that it should have I think.
hverkuil: Um, the commit log in that patch says how to do it :-)
<br> v4l2-ctl -c inject_vidioc_streamon_error=1
kbingham: hverkuil, ...
<br> ...
<br> Great. I knew I'd read it - and then I looked everywhere except right in front of me ...
<br> Well at least I wasn't dreaming ;-) thanks!
hverkuil: You're welcome!
<br> Note that the same issue can happen with the Request API, and I don't really know how to solve that. It's on my TODO list to figure this out, but it's a pretty low prio.
mort_: this particular command fails and I don't understand why: media-ctl -d /dev/media0 -l '"msm_csiphy1":1 -> "msm_csid1":0[1]'
<br> https://p.mort.coffee/Cr8.svg
<br> I'm able to connect csid1 to ispif1, ispif1 to vfe0_pix, and vfe0_pix to vfe0_video3
<br> but not csiphy1 to csid1
pinchartl: the graph looks very wrong
<br> the 6 yellow blocks at the top should be green
<br> they're subevs, they should have pads
mort_: they have pads according to the topolgoy
<br> topology*
pinchartl: what's the output of media-ctl -d /dev/media0 -p
mort_: https://p.mort.coffee/DLw
pinchartl: indeed. I wonder why the graphical representation is incorrect
mort_: I'm working on upgrading from linux 4.9 to linux 5.7, it looked about the same in 4.9 and everything worked
<br> I can put 4.9 on it and give you a graph from that if you want
pinchartl: does adding -v give you any extra information when you set the link with -l ?
mort_: oh wow, I tried running the csiphy1->csid1 link again and the kernel got unhappy: https://p.mort.coffee/DLQ
<br> now media-ctl hangs
<br> I'll reboot..
<br> video4linux likes to crash and hang linux in non-recoverable ways ime
<br> https://p.mort.coffee/KQb
<br> pinchartl
pinchartl: I'd blame the msm camera drivers :-)
<br> are you using a qcom bsp kernel ?
mort_: what sort of "permission system" is in use in the media controller API? I'm running this all as root
pinchartl: it's likely the driver returning that
mort_: I'm running this kernel: https://github.com/varigit/DART-SD410-kernel/tree/release/kernel-20.07
<br> it's for the variscite DART-SD410 SoC with a qualcomm snapdragon 410
<br> wouldn't surprise me if variscite's kernel is based on qualcomm's kernel
pinchartl: all my condolences, and good luck
mort_: are qualcomm kernels especially bad?
pinchartl: yes
<br> all bsp kernels are bad
<br> qcom is likely not the worst
<br> but probably not very far
mort_: well, would've been nice if linux itself supported any hardware
pinchartl: it would be nice if qcom submitted drivers to mainline
mort_: it would
pinchartl: Linaro has done a fairly good job in that area
<br> (and to be fair, qcom is helping there)
<br> have you tried running mainline on that board ?
mort_: no
<br> I could give it a shot, but it's not gonna work is it
pinchartl: there are camera drivers in the mainline kernel for that SoC
<br> they're limited in the features they support though
<br> you can capture raw data from the sensor, the ISP isn't supported
<br> so it depends what you want to do
mort_: to debug this driver in this qcom kernel I probably enable debugging from the driver somehow right
<br> for the driver for the csiphy1 specifcially
pinchartl: no idea, I haven't touched that kernel, I don't know what monsters lie beneath the surface :-)
<br> essentially, with a qcom kernel, we can't help at all
<br> you need to get support from qcom, or one of the service companies that support the qcom kernel
<br> what kind of sensor are you using ?
mort_: ov5645
pinchartl: that's a yuv sensor, right ?
mort_: yeah
<br> we usually configure it to give us nv12 frames
pinchartl: if I were you, I'd give mainline a try
<br> but I'm not you :-)
mort_: I'll try it out
<br> building torvalds/linux@v5.7 now
pinchartl: v5.7 is ancient
mort_: yeah ik
<br> it's the newest variscite kernel so it's what I've been using
pinchartl: if you try mainline, you can as well try v5.13
mort_: would fuck up some kernel patches
<br> I suppose I could get rid of those just to test
<br> I'll try 5.10, LTS is nice
<br> it's probably not gonna work though, devicetree stuff seems to change a lot
pinchartl: you can complain to variscite
***: camus1 has joined #linux-media
<br> camus has quit IRC (Remote host closed the connection)
mort_: ugh
<br> https://github.com/torvalds/linux/blob/v5.7/arch/arm64/boot/dts/qcom/msm8916.dtsi#L1623
<br> this label doesn't exist in 5.10
<br> I'll stick with 5.7, Linux changes way too much to be possible to upgrade just for a test
<br> tbh I don't get the point of devicetree if all the dtsi files you have to rely on change this frequently and this drastically
<br> <u>pinchartl</u>: well, with the upstream kernel, there's no /dev/media0 nor any /dev/video* devices
pinchartl: you won't like my answer, so I'll refrain from giving it
kbingham: hverkuil, "Tested-by: Kieran Bingham <kieran.bingham@ideasonboard.com>" for the "vb2 fix" patch - "
<br> hverkuil, noted in https://bugs.libcamera.org/show_bug.cgi?id=61, your patch using the stream on error injection on vivid no longer shows the "Dequeued an unexpected buffer" error message.
mort_: eh, you can say it. It's probably gonna be something about "you should've used a soc with better mainline support" or "you should've used mainline from the beginning and worked through these kinds of issues in mainline instead of in the fork" or something, and I don't disagree
***: camus has joined #linux-media
pinchartl: <u>mort_</u>: I won't repeat the long discussion from #armlinux here, thanks
mort_: alright
***: camus1 has quit IRC (Ping timeout: 480 seconds)
hverkuil: <u>kbingham</u>: OK, I'll clean up the patch and post it so it can be merged for the next kernel.
<br> Thanks for testing!
kbingham: hverkuil, Thanks for fixing, I saw a bug, logged it and before I knew it Laurent had talked to you and got a fix ;-)
mort_: it would've been useful to have a way to enable all dynamic kernel debugging except for the kind of things which spams continuously
***: GBenji has quit IRC (Quit: Leaving.)
<br> BrianG61UK has joined #linux-media
<br> gouchi has joined #linux-media
<br> NiksDev2 has quit IRC (Remote host closed the connection)
<br> NiksDev has joined #linux-media
<br> NiksDev has quit IRC (Remote host closed the connection)
<br> NiksDev has joined #linux-media
<br> NiksDev has quit IRC (Remote host closed the connection)
<br> NiksDev has joined #linux-media
<br> NiksDev has quit IRC (Remote host closed the connection)
<br> NiksDev has joined #linux-media
<br> camus1 has joined #linux-media
<br> camus has quit IRC (Ping timeout: 480 seconds)
<br> NiksDev has quit IRC (Remote host closed the connection)
<br> NiksDev has joined #linux-media
<br> svarbanov has quit IRC (Ping timeout: 480 seconds)
<br> camus has joined #linux-media
<br> camus1 has quit IRC (Ping timeout: 480 seconds)
<br> gouchi has quit IRC (Remote host closed the connection)
<br> jm_h__ has joined #linux-media
<br> jm_h has quit IRC (Ping timeout: 480 seconds)
<br> lucaceresoli has quit IRC (Quit: Leaving)
<br> jm_h__ has quit IRC (Remote host closed the connection)
<br> camus has quit IRC (Remote host closed the connection)
<br> camus has joined #linux-media
djrscally: <u>jmondi</u>: I checked how that sensor behaves running the cams in Windows; it actually has a lower HTS than output width there too
<br> Weird!
***: NiksDev has quit IRC (Ping timeout: 480 seconds)
<br> djrscally has quit IRC (Ping timeout: 480 seconds)