<!-- 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>

   pinchartl: <u>hverkuil</u>: ping, next try :-)
   hverkuil: <u>pinchartl</u>: pong
   pinchartl: I wanted to ask if you could have a look at the VIDIOC_ENUM_FMT extensions
   hverkuil: I'm rarely around here in the evening :-)
   pinchartl: they depend on Niklas' IO_MC cap
   <br> sure, I didn't necessarily expect you to be available yesterday, but I thought I'd try my luck just in case :-)
   hverkuil: I'll see if I can look at it today or tomorrow.
   pinchartl: thank you
   <br> I'd like to at least know if it goes in the right direction
   <br> as we have libcamera patches depending on it
   <br> including support for i.MX7 :-)
   <br> and qcom-dss
   <br> and allwinner
   hverkuil: What's the latest series? I see a v6 from March 19.
   pinchartl: that's the one
   <br> I've reposted Niklas' patches, and added the ENUM_FMT extension
   hverkuil: OK, I'll take a look.
   pinchartl: thank you
   <br> another topic I wanted to discuss
   <br> is CSI-2 VC/DT support
   <br> based on the multiplexed streams series that was posted last
   <br> for sensors generating embedded data, it requires the sensor to be split in 3 subdevs
   <br> one for the pixel source, one for the embedded data source, and one for the CSI-2 multiplexer
   <br> were you aware of that when reviewing the previous versions of the series, and is that ok with you ?
   hverkuil: I was aware of that. But I assume this is only needed for fairly advanced sensors, right? I.e. your average bog standard omnivision sensor shouldn't need this.
   <br> <u>pinchartl</u>: the ENUM_FMT patch looks good. It makes a lot of sense.
   pinchartl: <u>hverkuil</u>: many omnivision sensors can produce embedded data
   <br> including sensors that are already supported in mainline
   <br> so splitting those in multiple subdevs is a bit of a backward compatibility issue
   hverkuil: <u>pinchartl</u>: let's talk about that a bit more tomorrow.
   pinchartl: <u>hverkuil</u>: sure
   avbox111: My netbook (asus t101ha) has a ov2680 internal webcam. I can load 'uvcvideo', but I can't see any video device /dev/video0. I don't see any error message in demsg. Any ideas?
   ndufresne: <u>avbox111</u>: have you considered that this might not be a UVC camera ?
   <br> <u>avbox111</u>: I'll direct you to #libcamera (pretty much the only project targetting your HW)
   avbox111: <u>_abbenormal</u>: What else could it be then?
   ezequielg: <u>avbox111</u>: https://wiki.debian.org/InstallingDebianOn/Asus/T100TA
   <br> "The camera should be a mt9m114 camera device, it is currently not supported."
   avbox111: <u>ezequielg</u>: No, the camera is a ov2680, it is model t101HA, not T100TA.
   ezequielg: well, same thing.
   <br> it's most likely not UVC, but the sensor is connected to some IP block from Intel.
   <br> ov2680 is AFAICS not a camra, but a "sensor".
   avbox111: According what I see, the t100ta has 1368x768 pixel, the t101ha has 800x1280 pixel.