kbingham, ping
mchehab: can you (or hverkuil ) delegate venus patches to me, so that I can change their state in patchwork?
Kwiboo: great! I can definitely wait a few days.
and no, no plans for HEVC support yet
the next thing on our list is VP9
random question. Any ideas if there is any plan to move the AMD encoder drivers to v4l2 m2m?
I am thinking about the VCEs : https://github.com/obsproject/obs-amd-encoder/wiki/hardware-support
ribalda: no plans AFAIK.
hverkuil: :( and is anyone of AMD interested in linux-media? I have never met anyone from AMD at media summits. But I have never been outside Europe
Not a clue.
Converting a mesa vaapi driver into  v4l2 m2m is something doable in a reasonable amount of time?
Not a clue! :-)
Sorry, I know absolutely nothing about this.
I did more work on the capture card drive and now I've got 0 failures and warnings. :)
I did a bit of work on updating the tw9910 driver, but hit a snag. I want to be able to tell the driver how I want the chip to be configured, but I imagine that would mean editing the platform data structure.
Wouldn't that potentially break some drivers if I add more fields to the structure?
OnVar: should be fine: new fields would be 0 unless explicitly set by the bridge driver. So as long as '0' means 'keep the old behavior' it should have no effect on existing bridge drivers.
Alright, I wasn't sure about making the assumption that the structure would be zeroed out. Thanks.
Hi all, I'm intending on proposing a couple of patches working around an issue with the GEO GC6500 camera, and possibly others. Patches at https://github.com/digitalloggers/geocam-bpp/tree/master/camera-bpp/5 should apply to the media master branch. It would be nice to have your preliminary feedback before posting them to linux-media (issue previously discussed at https://linuxtv.org/irc/irclogger_log/v4l?date=2019-08-22,Thu&sel=87#l83).
pinchartl: your input especially welcome:) ^
doublef: hello! I think you are fine posting those patches on the mailing list. Discussion can happen directly there.
Discussing things in the mailing list is actually encouraged, as it makes the work transparent to others.
doublef: please CC me when posting the patches
ezequielg: pinchartl: thanks, will prettify and post them.
kos_tom, I'm afraid we haven't looked at the DRM side for GMSL yet. There's always too much overlap between DRM/V4L2 on video :D
mani_s, Hola, how can I help
mani_s, Aha - I see you're asking over in #96boards about where the enable pin is on the max9286. Do you mean something like pin 47 (!PWDN)? (Page 19 in my datasheet)
kbingham, just playing w/ your gmsl patches and fixed one issue which stopped me from using max9286 on db410c :D
wondering if I can propose a patch for that or you can integrate it in your next version!
mani_s, Certainly!
I think you could either send your patch in reply to the latest max9286 series or just post it, clearly marked that it depends on the MAX9286 driver.
kbingham, thanks! will do. it is a one line fix btw!
kbingham, one more question: what kind of changes are required to convert a v4l2 platform driver to use vc? I'm currently looking at qcom camss
Excellent - should be easy then :) - Please cc neg : "Niklas Söderlund <niklas.soderlund@ragnatech.se>", as he has also worked on this driver recently.
mani_s, I think VC is becoming a big topic that's had a few rounds of development and discussions already. It may need some further dedicated development resourcing too. I believe jmondi is our current resident expert on VC and owns the latest published series.
kbingham, okay, then I'll wait for it to become stable then ;-)
kbingham: my understanding is that we're back at square zero on VC
jmondi, Excellent. Just like I said, you're the resident expert :D
kbingham: yes, we've never reached an agreement on how to move forward :-(
Apologies for that random link, I did something silly
Logitech Brio Led Controls not showing up:
Using kernel 5.2.17 with fedora 30
The followinging modes for led contron do not show upled1_mode (menu)   : min=0 max=3 default=0 value=3
                 led1_frequency (int)    : min=0 max=255 step=1 default=0 value=0
any idea on this?