Re: Future of the SAA7146 drivers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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'.

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, with a big fat notice that
these APIs are now av7110 specific (as they have almost always been in
practice).

Regards,

	Hans

> 
> Regards,
> Stefan
> 
> 
> 
> On 02.02.23 22:26, Stefan Herdler wrote:> Hi Hans, Sören,
>>
>> On 02/02/23 10:43, Soeren Moch wrote:
>>> Hi Stefan, Hans,
>>>
>>> On 02.02.23 00:12, Stefan Herdler wrote:
>>>> Hi Hans, Sören,
>>>>
>>>> On 01/02/23, 10:15 Hans Verkuil wrote:
>>>>
>>>> [...]
>>>>>
>>>>> Once it is converted to vb2 the driver can stay.
>>>>>
>>>>> Note that the driver might need a bit more work: we use the
>>>>> v4l2-compliance
>>>>> utility to test V4L2 API compliance of a driver, and after the vb2
>>>>> conversion the driver should pass this test. So the compliance test
>>>>> might
>>>>> find some other things that do not work as they should, and it would be
>>>>> really good to clean that up as well. Usually the things it finds are
>>>>> pretty
>>>>> easy to fix.
>>>>>
>>>> For the records, as long I remember it:
>>>> The "Buget Patch" driver is superfluous and can be removed.
>>>> This driver is for an experimental hardware-mod which never really
>>>> worked. No such hardware was ever produced.
>>>> I was really surprised to see it.
>>> I own such card, as I wrote earlier. The budget patch works great and is
>>> necessary for such cards. Please keep it.
>>>
>> I think you confused it with is successor "fullTSmod" which works great
>> indeed.
>>
>> The support for the "fullTSmod" is implemented in the "dvb-ttpci" kernel
>> module.
>> The "Buget Patch" driver is an separate kernel module.
>>
>>  From Kkonfig:
>> config DVB_BUDGET_PATCH
>>      [...]
>>        Support for Budget Patch (full TS) modification on
>>        SAA7146+AV7110 based cards (DVB-S cards). This
>>        driver doesn't use onboard MPEG2 decoder. The
>>        card is driven in Budget-only mode. Card is
>>        required to have loaded firmware to tune properly.
>>        Firmware can be loaded by insertion and removal of
>>        standard AV7110 driver prior to loading this
>>        driver.
>>
>> I my self own and operate a card with "fullTSmod" too. An I did some
>> mods for others.
>> I never loaded the "Buget Patch" driver.
>> And the kernel module it isn't loaded on my VDR. I checked it right now
>> again.
>>
>> I removed the "budget-patch.ko" and everything kept working like usual.
>> Ill keep an eye on it.
>>
>> Regards,
>> Stefan
>>
>>
>>
>>
>>> Regards,
>>> Soeren
>> [...]




[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux