| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | asharma has left | [08:51] |
| ........ (idle for 36mn) | ||
| ezequiel1 has quit IRC (*.net *.split)
mripard has quit IRC (*.net *.split) | [09:27] | |
| ......................................... (idle for 3h24mn) | ||
| sailus | hverkuil: Hello! | [12:51] |
| hverkuil | sailus: hi!
(just out of two meetings) | [13:05] |
| sailus | hverkuil: How are you doing? | [13:16] |
| hverkuil | good, thanks. Hope you're OK as well! | [13:29] |
| sailus | I'm doing good, thanks!
About the V4L2 fwnode patches --- I've sent a new pull request to Mauro. But you had taken patches to your tree that depend on the patches in the pull request. Would it be possible to rebase yours on my new tree? For this time only, that is. | [13:31] |
| hverkuil | I did :-) | [13:34] |
| sailus | Good. :-) | [13:34] |
| hverkuil | But I didn't mention your patches in my pull request, but if Mauro want he can get all from my pull request. | [13:34] |
| sailus | You may have also noticed that there are quite a few drivers developers from Intel have submitted recently. There's at least one more to come in the near future.
I can pick them up and submit a pull request eventually if you're fine with that. | [13:36] |
| hverkuil | let's postpone that decision for 1-2 weeks.
Very good to see all this Intel activity! | [13:41] |
| sailus | Works for me.
One more matter: Philipp has had his media-ctl patches for setting frame rate on all pads plus colour space and quantisation. I've reviewed them but there have been no other comments. I'll push them to v4l-utils unless you have concerns. It's "[PATCH v4 1/4] media-ctl: add pad support to set/get_frame_interval" and the three other patches. | [13:44] |
| hverkuil | Yes, go ahead. You can add my 'Acked-by: Hans Verkuil <hans.verkuil@cisco.com> | [13:51] |
| sailus | Ack. Thanks! | [13:53] |
| .... (idle for 19mn) | ||
| pH5 | hverkuil, sailus: thanks! | [14:12] |
| ............ (idle for 55mn) | ||
| hverkuil | mripard: CEC low level monitoring on the A10 works great! I'm really surprised how accurate it is, much better than I expected.
Thanks for all the great work getting drm up and running, that's been very useful. | [15:07] |
| ..... (idle for 22mn) | ||
| koike | hverkuil: hi o/, about your last comment in vimc regarding link validation of colorspace. The example you send just propagate the colorspace from sink to source within an entity (unless I misread the patch), but what about different colorspaces (and all the other colorimetry params) between source and sink of different entities connected by a link ? | [15:29] |
| .... (idle for 16mn) | ||
| hverkuil | I'm not sure if the default link validation checks those fields. I guess it should. Within a block (say a scaler) it should not be allowed to have differences between the source and sink colorspace information, unless the block is a colorspace converter, of course.
But I don't believe this is checked today in any of the subdev drivers. | [15:45] |
| mripard | hverkuil: awesome :) | [15:55] |
| *** | benjiG has left | [16:05] |
| ..................... (idle for 1h42mn) | ||
| koike | hverkuil: sorry, I had to leave. The v4l2_subdev_link_validate_default doesn't check for colorimetry, that is why I implemented a custom link_validate in the vimc driver, I can send a patch adding this check in the v4l2_subdev_link_validate_default then
in vimc I already propagate the format from sink to source within that block, only the sensor and capture blocks this doesn't make sense as they have a single pad | [17:47] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |