| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| koike | hverkuil: sorry, I was off last week, sure, I'll take a look | [05:44] |
| ..................... (idle for 1h44mn) | ||
| bbrezillon | hverkuil: pong (5 days later :-/) | [07:28] |
| hverkuil | bbrezillon: I was wondering if you can prepare some slides for the 'Future work' media session at the ELCE?
Quick intro to the proposed changes, and esp. open questions. | [07:29] |
| bbrezillon | We're just talking about the EXT_BUF ioctl()s, right? | [07:33] |
| hverkuil | Yes. Your RFC v3. | [07:33] |
| bbrezillon | I prepare 2 or 3 slides, yes | [07:34] |
| hverkuil | Thank you, much appreciated! | [07:34] |
| bbrezillon | *I can prepare | [07:35] |
| ...... (idle for 29mn) | ||
| KitsuWhooa | I'm trying to finish up support for a saa7134-based card I have and I'm working on DVB-T. Firmware upload and communication with the frontend seems to be fine: [ 3887.313879] tda1004x: found firmware revision 29 -- ok. debug=1 in tda1004x shows successful I²C transfers
There are no errors anywhere that I can see, however when trying to tune with dvbscan, I get "Unable to query frontend status", after the FE_READ_STATUS ioctl which returns 0 according to strace Any idea what the issue might be/how I should approach this? | [08:04] |
| hverkuil | dafna2: ping | [08:15] |
| KitsuWhooa | ...maybe dvbscan is broken, because it seems to throw the same error on my RTL2832U which I know works in VLC | [08:19] |
| ......... (idle for 43mn) | ||
| Okay, I switched to scan. It seems to be able to tune to a frequency but it doesn't list any services (that are known to exist using a known working device). Instead I get WARNING: filter timeout pid 0x....
https://tasossah.com/gb7131_scan.txt | [09:02] | |
| hverkuil | paulk-leonov: ping | [09:02] |
| ........ (idle for 36mn) | ||
| bbrezillon | hverkuil: https://gitlab.collabora.com/bbrezillon/v4l2-ext-fmt-buf-slides/blob/master/v4l2-ext-fmt-buf-ioctls.pdf
let me know if you want something with more detailed s/with// | [09:38] |
| hverkuil | bbrezillon: add a slide with 'open questions'. Looks good otherwise.
bbrezillon: and upload with a right suffix: it wasn't a pdf :-) | [09:51] |
| .... (idle for 19mn) | ||
| bbrezillon | hverkuil: fixed | [10:10] |
| bingbu | Does any meet code pull failure from git://linuxtv.org/media_tree.git today? | [10:16] |
| hverkuil | tfiga: ping
bingbu: works for me. | [10:18] |
| tfiga | hverkuil: pong | [10:20] |
| hverkuil | tfiga: thanks for your replies and thoughts about the future API. Much appreciated. | [10:21] |
| bingbu | hverkuil: thanks, likely something wrong with my proxy. | [10:21] |
| hverkuil | See also my reply to the ANNv2: I think we need a brainstorm session for this since there is no way we can ever come to a conclusion in just 4 hours next week.
It would be very useful to include you in such a brainstorm session, so think about when that would work for you. Most of the other stakeholders are nicely concentrated in Europe, so it tends to be easier to find a date that works. You're a bit further away, though :-) | [10:22] |
| tfiga | hverkuil: I might be a bit busy in November and December is a bit of a holiday season (and I need to spend my vacation balance...), but Jan/Feb should work for me
anywhere with a good connection to Poland would be appreciated ;))) | [10:25] |
| hverkuil | December is out for me as well. But I was thinking about the week before FOSDEM in Brussels. | [10:26] |
| tfiga | and Google Tokyo is always open to host us ;)
we got a really nice new office recently otherwise, the week before FOSDEM might be a good ide idea* | [10:26] |
| hverkuil | I'd be fine with Tokyo, but I suspect the cost will be a problem for others. | [10:28] |
| tfiga | yeah, given how many people are based in Europe, that's not the most convenient option
(and not the cheapest) that said, we would at least have lunches included ;) | [10:28] |
| hverkuil | If we go with Brussels, then we need to find and book a hotel and conference room very soon after the ELCE, to keep the cost down. | [10:30] |
| tfiga | anyway, let's maybe see what level of interest we get | [10:30] |
| hverkuil | paulk-leonov: ping | [10:31] |
| ..... (idle for 20mn) | ||
| tfiga: stateless decoder spec just got merged! mchehab: much appreciated!
gnurou: ^^^^ Many thanks to everyone who worked on this. | [10:51] | |
| jernej: ping | [11:04] | |
| jernej: mailed you: v4l2-compliance claims that your deinterlace driver supports scaling, but I think that's wrong.
So it's either a driver bug or a compliance test bug. Most likely the latter. | [11:16] | |
| tfiga | hverkuil: \o/
thanks everyone | [11:19] |
| paulk-leonov | hverkuil: pong
oh nice :) | [11:29] |
| hverkuil | paulk-leonov: did you see mchehab's comments on the HEVC series? Do you think you can look at that this week? It shouldn't be difficult.
It would be great if that can be merged before the ELCE. | [11:29] |
| paulk-leonov | hverkuil: yes it looks doable for me to send a new version
indeed | [11:30] |
| hverkuil | paulk-leonov: Mauro also had comments about the use of (1 << X) for the 64-bit 'flags' fields. He preferred (1ULL << X). This was in an irc discussion over on #media-maint.
https://linuxtv.org/irc/irclogger_log/media-maint?date=2019-10-17,Thu | [11:32] |
| paulk-leonov | hverkuil: understood, thanks for the context | [11:33] |
| hverkuil | If you post a new series anyway, then just change that too. I don't quite agree with Mauro :-) but it is certainly not wrong or worth spending time on.
ribalda: ping | [11:33] |
| paulk-leonov | sure | [11:35] |
| ribalda | hverkuil: pong! | [11:37] |
| hverkuil | Hi Ricardo! I wonder if you have time to add a test control of the new AREA type to vivid, and add support for it to v4l2-ctl and (if needed) v4l2-compliance?
That way this new type is actually regression tested. | [11:39] |
| ribalda | sure | [11:39] |
| hverkuil | I should have mentioned this before, sorry for the late comment. | [11:39] |
| ribalda | no worries at all. Can you give me 1 week? | [11:40] |
| hverkuil | I've just sync v4l-utils to the latest headers, so that's why this cropped up now.
Sure. | [11:40] |
| ribalda | I havent touched before v4l2-ctl, so I probably fuck it up :) | [11:40] |
| hverkuil | Do vivid first, then v4l2-ctl, and v4l2-compliance last (this may not be needed at all)
vivid already has test user controls for all standard types (v4l2-ctl -l), so just add an area control. | [11:41] |
| ribalda | if you merge (or at least intent to merge) the last one (for custom areas) I could add 2 controls
1 for the pixel size 1 for setting the area for the autos the first one (pixel size) is read only, the second is read-write. and will show how to use https://patchwork.linuxtv.org/patch/59505/ | [11:43] |
| hverkuil | You are not recreating V4L2_CID_UNIT_CELL, this is just to test the control type. So you add a VIVID_CID_AREA control (vivid-ctrls.c), which is otherwise meaningless. | [11:44] |
| ribalda | to add VIVID_CID_AREA I need https://patchwork.linuxtv.org/patch/59505/ . Otherwise I can only add UNIT_CELL | [11:45] |
| hverkuil | The key thing is that you should be able to set/get it with v4l2-ctl.
Yes, you need some form of that patch :-) I'll reply to your proposal. That patch can be the first patch in a series adding vivid support. | [11:46] |
| ribalda | ferpect!, lets do it like that | [11:47] |
| ...... (idle for 27mn) | ||
| hverkuil | koike: ping | [12:14] |
| ..................... (idle for 1h42mn) | ||
| mjourdan- | hverkuil: there are a few more complications to fixing the corner case I'm having. I sent an email in the same thread 3 days ago but you answered the previous one, so unsure if you saw it. | [13:56] |
| hverkuil | mjourdan-: I didn't see it, thanks for pointing it out. | [13:57] |
| ........... (idle for 52mn) | ||
| jernej | hverkuil: H3 deinterlacer does indeed support scaling, so it's not a bug.
it also supports color adjustment via CSC matrix and pixel format conversion, but that's not really implemented mostly because there is no good documentation and BSP driver doesn't support that well, proposed mainline driver supports converting NV12 input to NV21 and vice versa, but that's it | [14:49] |
| hverkuil | jernej: OK, good to know. Is it mentioned somewhere explicitly in e.g. the Kconfig entry and source that this driver supports scaling? (Sorry, didn't check this). | [14:53] |
| jernej | No, there is no explicit mention of scaling. I didn't know it should be | [14:55] |
| shuah | hverkuil: Hi Hans! Here is the autogenerated regression tests git repo announcement - https://lkml.org/lkml/2019/10/15/756
Also link to the e-curse for new developers - https://training.linuxfoundation.org/training/a-beginners-guide-to-linux-kernel-development-lfc103/ This is a free e-course I wrote for beginners | [15:00] |
| hverkuil | jernej: In any case, the remaining issues are tiny, so I'll take the v5. | [15:08] |
| ...... (idle for 29mn) | ||
| jernej | hverkuil: so scaling capability must be mentioned or not? | [15:37] |
| hverkuil | It should be mentioned in the Kconfig (it's not at the moment), and in the driver. I see that the comment at the top says:
+ * Allwinner sun8i deinterlace driver That should be: + * Allwinner sun8i deinterlace and scaler driver | [15:38] |
| jernej | hverkuil: Why? scaling is not standalone feature
at least I understand your suggestion in a way that you could only do scaling, which isn't true well, there might be a way, but HW wasn't designed with that in mind | [15:47] |
| hverkuil | Ah, good point. Hmm, how to phrase this.
"Allwinner sun8i deinterlacer with scaler driver" perhaps? | [15:54] |
| jernej | ok | [15:57] |
| hverkuil | The point is that this feature is unusual for a deinterlacer, so it should be mentioned somewhat prominently. | [15:59] |
| ............................ (idle for 2h18mn) | ||
| savo | Hi, some of the key codes are above 255 on my Bluetooth remote so i use ir-keytable to remap them. This has just stopped working with v1.18. I think its the removal of --device argument | [18:17] |
| ........................................................... (idle for 4h50mn) | ||
| *** | hnrk has quit IRC (Quit: Lost terminal) | [23:07] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |