Em Mon, 6 Feb 2023 01:06:47 +0100 Stefan Herdler <herdler@xxxxxxxxxxxxxx> escreveu: > Hi Hans, > > On 03/02/23 09:50, Hans Verkuil wrote: > > On 03/02/2023 01:58, Stefan Herdler wrote: > >> Hi Hans, > >> > >> It's me again, sorry. > >> > >> Sören wrote to me that he dislikes the idea of driver specific > >> headerfile and will refuse to maintain the driver if there is any change. > >> > >> I can't tell more, I'm just the messenger, sorry. > > > > No problem, I think we'll just leave it as-is. > > > > The reality is that 1) there are very few developers with in-depth DVB > > knowledge in the media subsystem, and 2) they don't have time. > > Sörens "no changes" means absolutely no changes. > That includes filenames, position, basically everything. It won't make any sense to warrant that any Kernel files will be kept as-is forever. If one wants a fixed driver, just use a LTS distro. > His main concern is that distributions may packages if build brakes. > I wasn't aware of that since Friday. (Poor communication, sorry.) Distributions can handle changes on Kernel files, provided that any changes would also be applied at the userspace apps (if this is the case). > This concern is not completely unjustified. > Especially if it happens without notice and no update is available. > > The download links of the vdr-plugin seems to be broken, which might be > fatal in this case. > It happened this summer when vdr switched from FTP to GIT. I suppose it > was inadvertently and can be fixed quickly. > I'll take care of it, a missing source isn't good anyway. > > Until today I wasn't aware of that either. > I focused on the kernel and used a local copy so far. > > > > > Also, the DVB drivers that are in the kernel seem to be doing fine: > > bug reports are rare. This videobuf issue is the first in years that > > cropped up and this too is really only analog video as well, it's just > > that it affects DVB boards as well since the same driver is used. > > > > The av7110 has always been an unusual card and some API decisions were > > made in the past that do not fit well into our current ideas how this > > should work. But frankly, I personally have no interest in getting > > involved in that 'fight'. > > Me neither. > But it looks like I already managed to get between the lines :-(. > > > > BTW, I looked at your av7110api.diff patch and that is a good first step. > > I do thing that the existing video.h/audio.h/osd.h should be replaced > > with versions that just include av7110.h, > > For clarification: > I mentioned the API-conversion under the impression the av7110 driver is > almost already gone and that it might be the only chance to save it. > I do not really want this conversion, I still prefer to avoid it. > But if the choice is between driver removal and API-conversion, I'll > take the latter. > > Please inform us early, if Linux-Media decides the API-conversion is > necessary and has to be done. > I guess it takes at least 1/2 year to distribute the updates. > Unfortunately, Sören most likely won't be "in the boat" anymore, in this > case. But that is his own decision. > > Anyhow, this is topic for later, as you wrote recently. > First thing to do is the videobuf conversion. > > In the next weeks I'll be busy with other things and probably don't find > much time for this hobby. > But other modifications to the driver doesn't make much sense while > videobuf conversion is in progress anyway. > > Please cc me if you're done with videobuf conversion. I might overlook > it otherwise. > I'll take a look at the compliance-tool then and try to fix as much I can. > > > with a big fat notice that > > these APIs are now av7110 specific > Don't worry there are only the 2 fullfeatured-cards using this API and > just because of historical reasons. The driver of the "new" > HD-fullfeatured-card dates back to 2008 (*). > Meanwhile here have been written several specific output-device-plugins > for vdr using V4L-API, vaapi, vdpau, ... > There are no plans to use this part of the DVB-API ever again. Ok. If that's the case, maybe we can just keep the api without changes. Yet, in order to move av7110 out of staging, we should finish documenting the API (or drop the unused/undocumented parts of it). > (* The driver is out-of-tree and doesn't count. It is just about the date.) > (as they have almost always been in > > practice). Thanks, Mauro
