| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | hfr has left | [12:43] |
| .......................... (idle for 2h6mn) | ||
| tfiga has quit IRC (Remote host closed the connection) | [14:49] | |
| ...... (idle for 27mn) | ||
| pinchartl | hverkuil: ping | [15:16] |
| hverkuil | pinchartl: pong | [15:17] |
| pinchartl | v4l_fill_fmtdesc() names V4L2_PIX_FMT_DV "1394". the uvcvideo driver, however, can differentiate between SD-DV, SDL-DV and HD-DV, as well as between 50Hz and 60Hz. it currently uses that information to construct the format name
I'd like to remove format names from uvcvideo, but that information would then be lost what do you think should be done about that ? | [15:17] |
| hverkuil | What does V4L2_PIX_FMT_DV mean at all? It's part of the 'Reserved Format Identifiers' and in the 'Details' column all it says 'Unknown'
(meeting) | [15:20] |
| pinchartl | https://en.wikipedia.org/wiki/DV I assume :-)
IEC 61834 (take your time, there's no hurry) | [15:20] |
| .... (idle for 15mn) | ||
| hverkuil | Ah, it's a compressed stream. I should have remembered that.
If the driver fills in the name, then the core won't overwrite it. So this might be one case where the uvc driver can still fill in the name. It just needs a good comment why this is still filled in manually. While you're at it: a patch to replace 'Unknown' with something more descriptive would be welcome :-) | [15:35] |
| pinchartl | I think the core only keeps the name if the format is unknown
but V4L2_PIX_FMT_DV is known, so the core will overwrite the name | [15:40] |
| hverkuil | It shouldn't. There are lots of drivers that still fill in the description. | [15:40] |
| pinchartl | look at v4l_fill_fmtdesc() :-) | [15:41] |
| hverkuil | You're right. | [15:42] |
| pinchartl | sorry about that :-D
5d8d8db851ef81337e7026b32a9d5a9cfb2271d5 ("UVC: Add support for R200 depth camera") got merged without documentation :-( | [15:42] |
| hverkuil | Hmm, uvc is the only one using that format. | [15:43] |
| pinchartl | ah no, just without names in v4l2-ioctl.c
the DV format ? | [15:44] |
| hverkuil | yes | [15:44] |
| pinchartl | didn't we use to have a V4L driver for firewire ?
it's all in userspace now | [15:45] |
| hverkuil | Seems to be a DVB driver. I never touched it. | [15:46] |
| pinchartl | and it wasn't V4L2
drivers/firewire/video1394.c (long gone) anyway, yes, it looks like uvcvideo is the only one I wonder if new 4CCs should be introduced for the SD, SDL and HD variants there's little public documentation though I hate how IEC standards are not available for free | [15:46] |
| hverkuil | The format in memory is the same for all? | [15:48] |
| pinchartl | for SD and SDL it would appear to be
DV frames are divided in "DIF block sequences" a DIF sequence consists in a number of 80 bytes DIF block the number of DIF sequences per frame depends on the scanning rate and resolution (SD/SDL/HD) (I'm still trying to figure out what SDL means) Standard Definition - Long according to RFC3189 | [15:52] |
| hverkuil | I am inclined not to spend much time on this: print the detected format in a debug message, but otherwise just keep the description that the core sets.
I guess you don't have any actual hardware that can create such a stream? Anyway, I'm going home. ttyl | [16:04] |
| pinchartl | I actually have an old camera that can produce DV data | [16:19] |
| .......... (idle for 49mn) | ||
| *** | benjiG has left | [17:08] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |