linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Soeren Moch <smoch@web.de>
To: Stefan Herdler <herdler@nurfuerspam.de>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	linux-media@vger.kernel.org
Cc: Manu Abraham <abraham.manu@gmail.com>,
	Tomasz Maciej Nowak <tmn505@gmail.com>,
	Corinna Vinschen <vinschen@redhat.com>
Subject: Re: Future of the SAA7146 drivers
Date: Thu, 2 Feb 2023 10:43:32 +0100	[thread overview]
Message-ID: <df796e6c-c82f-8734-3de6-8446bd0b48ab@web.de> (raw)
In-Reply-To: <8fb1799b-5ed1-9d26-54fc-b47abe0c13cf@nurfuerspam.de>

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.

Regards,
Soeren
>>>
>>> There is a long lasting controversy about the deprecated 3
>>> DVB-API-files
>>> for the av7110 driver.
>>> Sören stated he is tired about that discussions and looking for
>>> permanent solution without having to rewrite the whole driver.
>>>
>>> In this case I'm just the messenger, but I would also prefer a
>>> permanent
>>> solution.
>>> That is why I made the suggestion with the driver specific UAPI file.
>>> The av7110 driver is only driver using this API-part.
>>> And the modification is fairly easy and the impact minimal.
>>>
>>> May that be a compromise all parties can live with?
>>
>> Moving it to a public av7110.h header makes sense to me.
>
> I've done this already.
> Primary for my self to see if and how it may work.
> I'll attach the patch, maybe it is helpful.
>
> Theoretically there shouldn't be a difference whether the headers are in
> 1 or 3 files.
> Unused symbols should be removed by the compiler while optimization the
> result should be identical.
> I was just curious and decided to try it.
>
> Unfortunately I couldn't test it yet. But hopefully next weekend.
> There seems to be an issue with new kernel and my Nvidia graphics-card.
> But the kernel builds and boots into text console.
>
>>
>> It's a nice-to-have in my view, and moving it to a driver-specific API
>> should avoid future discussions. The fact remains that as long as
>> people use this API we can't remove it, however much we would want to.
>>
>> I think the main problem has always been that we are surprised at how
>> many people still use these cards. It's very similar in that respect
>> to the bttv driver: very old, but still in use.
>
> I own one too.
> Such cards can still be handy for digitizing family videos and stuff.
>
>>
>> The difference appears to be that the use of saa7146 cards is confined
>> to a specific region (esp. Germany), whereas bttv is in use worldwide.
>
> Until recently I wasn't aware that there are no saa7146 cards for ATSC
> nor ISDB.
>
>>
>> Because of that we just miss that it is still in use.
>>
>> Having an active maintainer should help with that.
>>
>> Regards,
>>
>>     Hans
>
>
>
>
>
> On 01/02/23, 14:51 Hans Verkuil wrote:
>
> [...]
>>
>> It's the analog video streaming that uses vb2, so being able to test
>> that
>> is critical.
>>
> The DVB data always uses one specific of the 2 video ports. The other
> one is not able to handle DVB-data.
> It is always the path through BRS and FIFO3, if I remember correctly.
>
> The analog video data has to use the remaining video port and FIFO1 if a
> DVB-Tuner is present.
> Input data format is YUV and output RGB. At least at the FF cards.
>
> (I may have confused the Ports, but in general it should be correct.)
>
> I don't have a combined budget-card and don't know how the driver
> handles analog inputs. But because of this hardware limitation there
> shouldn't be much difference between the decoded video of the FF and the
> video-input of a combined DVB-budget.
> Maybe testing on a FF is sufficient?
>
>
>> So I decided to do this differently:
>>
>> 1) I'll revert the move of saa7146 to staging, it will go back to
>>     mainline. av7110 stays in staging for now (that might change, I
>>     just don't want to make more changes than strictly necessary).
>>
>> 2) I will do the vb2 conversion. I have the analog video hardware,
>>     so I can test this.
>>
>> I didn't want to spend time on that originally, but since these drivers
>> are still in use, it is probably best if I bite the bullet and just
>> do it.
>>
>> I'm now almost done with the vb2 conversion of cx18, and it was about
>> 2 days work, which isn't that bad. I'll try to get this saa7146 vb2
>> conversion done this month.
>>
>> The PR reverting this has just been posted:
>>
>> https://patchwork.linuxtv.org/project/linux-media/patch/5902a4f2-da31-816c-f3cf-020340dbaddf@xs4all.nl/
>>
>>
>
> Great news, thanks!
>
> Regards
>
> Stefan
>
>> Regards,
>>
>>     Hans


  reply	other threads:[~2023-02-02  9:50 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 22:19 Future of the SAA7146 drivers Stefan Herdler
2023-01-31  8:45 ` Hans Verkuil
2023-01-31 23:56   ` Stefan Herdler
2023-02-01  9:15     ` Hans Verkuil
2023-02-01 11:35       ` Soeren Moch
2023-02-01 13:51         ` Hans Verkuil
2023-02-01 15:20           ` Soeren Moch
2023-02-01 16:37             ` Hans Verkuil
2023-02-08  8:42               ` Mauro Carvalho Chehab
2023-02-01 23:12           ` Stefan Herdler
2023-02-02  9:43             ` Soeren Moch [this message]
2023-02-02 21:26               ` Stefan Herdler
2023-02-03  0:58                 ` Stefan Herdler
2023-02-03  8:50                   ` Hans Verkuil
2023-02-06  0:06                     ` Stefan Herdler
2023-02-08  9:08                       ` Mauro Carvalho Chehab
2023-02-12 23:10                         ` Stefan Herdler
2023-03-24 10:37                           ` saa7146: please test the vb2 conversion! Hans Verkuil
2023-03-24 10:40                             ` Hans Verkuil
2023-03-24 21:21                               ` Stefan Herdler
2023-03-27 17:13                                 ` Tomasz Maciej Nowak
2023-04-06 22:43                                 ` Stefan Herdler
2023-04-07  7:04                                   ` Hans Verkuil
2023-04-09 22:36                                     ` Stefan Herdler
2023-04-11  7:29                                       ` Hans Verkuil
2023-04-12 10:11                                       ` Hans Verkuil
2023-04-12 11:16                                         ` Hans Verkuil
2023-04-14  0:15                                           ` Stefan Herdler
2023-04-14  8:36                                             ` Hans Verkuil
2023-04-15 21:15                                               ` Stefan Herdler
2023-03-25  1:44                           ` [PATCH] Legacy DVB API: completion of documentation Stefan Herdler
2023-03-25  8:47                             ` kernel test robot
2023-03-26 21:34                             ` [PATCH v2] " Stefan Herdler
2023-03-27 18:28                               ` Mauro Carvalho Chehab
2023-04-02 22:25                                 ` Stefan Herdler
2023-07-17  2:04                                 ` [PATCH v3 0/6] " Stefan Herdler
2023-07-17  2:04                                   ` [PATCH v3 1/6] Add documentation for legacy DVB decoder API Stefan Herdler
2023-07-17  2:04                                   ` [PATCH v3 2/6] Add documentation for osd.h Stefan Herdler
2023-07-17  2:04                                   ` [PATCH v3 3/6] Add documentation for audio.h (data types) Stefan Herdler
2023-07-19  9:09                                     ` kernel test robot
2023-07-17  2:04                                   ` [PATCH v3 4/6] Add documentation for audio.h (function calls) Stefan Herdler
2023-07-17  2:04                                   ` [PATCH v3 5/6] Add documentation for video.h (data types) Stefan Herdler
2023-07-17  2:04                                   ` [PATCH v3 6/6] Add documentation for video.h (function calls) Stefan Herdler
2024-01-28 23:32                                 ` [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 1/6] " Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 2/6] media: docs: uAPI: dvb/osd: " Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 3/6] media: docs: uAPI: dvb/audio: completing the documentation (data types) Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 4/6] media: docs: uAPI: dvb/audio: completing the documentation (function calls) Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 5/6] media: docs: uAPI: dvb/video: completing the documentation (data types) Stefan Herdler
2024-01-28 23:32                                   ` [PATCH v4 6/6] media: docs: uAPI: dvb/video: completing the documentation (function calls) Stefan Herdler
2024-02-07  5:10                                   ` [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation Mauro Carvalho Chehab
2024-02-08 23:56                                     ` Stefan Herdler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=df796e6c-c82f-8734-3de6-8446bd0b48ab@web.de \
    --to=smoch@web.de \
    --cc=abraham.manu@gmail.com \
    --cc=herdler@nurfuerspam.de \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=tmn505@gmail.com \
    --cc=vinschen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).