On 8/16/19 10:06 AM, Hans Verkuil wrote: > Rather then discussing topics for a meeting under the subject 'Lisbon' > let's start a new thread referring to the right place :-) > > I will try to organize a room, either during the ELCE or (if that doesn't > work) perhaps on the Thursday afterwards. If that's going to be a problem > for someone, please let me know. I can only get a room for Thursday afternoon (2pm-6pm). I'm inclined to take that room, but if a lot of people who want to come, will already have left on the Thursday, then there is no point in me reserving this room. So if you are unable to attend on Thursday, then please let me know asap! If Thursday is no problem, then I wanted to have more informal meetings somewhere in the conference center during the morning, and after lunch use the room. If Thursday is a no-go, then we will just have to find a place inside the conference center during the ELCE. Regards, Hans > > I do need to know how many people I can expect. I have the following > confirmed attendees (and please reply if you are not listed!): > > Alexandre Courbot <acourbot@xxxxxxxxxxxx> > Tomasz Figa <tfiga@xxxxxxxxxxxx> > Jacopo Mondi <jacopo@xxxxxxxxxx> > Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > Hans Verkuil <hverkuil@xxxxxxxxx> > > I know there were more who mentioned on irc that they would attend, > but it is easier to keep track if I have it in an email. > > Topics posted under the previous thread: > > Tomasz: > > I would want to discuss various v4l2_buffer improvements, e.g. > - DMA-buf import with plane offsets, > - unifying the buffer structs for M and non-M formats, > - ability to import different FDs with offsets for non-M formats if the > layout matches driver expectations, etc. > > Besides that, I would be interested in the general idea on handling > complex cameras in the Linux kernel in spite of the remaining V4L2 > limitations, e.g. > - combinatorial explosion of /dev/video nodes, > - significant ioctl overhead, > - huge amount of historical legacy making the driver and userspace > implementations overly difficult and prone to repetitive mistakes, > - the above also limiting the flexibility of the API - formats, frame > rates, etc. set using distinct APIs, not covered by Request API, with > non-failure "negotiation hell", etc. > - lack of fences, etc. > > Jacopo: > > Apart from discussing libcamera and hope we could kickstart a review of > its API, I would like to re-start discussing multiplexed stream support, > but that would require Sakari to be there, something I'm not certain > about. Sakari? > > Alexandre: > > If Collabora/Bootlin is there, I'd certainly want to discuss stateless > codecs, in particular m2m codec helpers and finalize the specification > in general. > > Regards, > > Hans >
