From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Soeren Moch <smoch@web.de>,
Stefan Herdler <herdler@nurfuerspam.de>,
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: Wed, 1 Feb 2023 14:51:57 +0100 [thread overview]
Message-ID: <d9197b80-335c-ee70-eccc-ad04c026cbc9@xs4all.nl> (raw)
In-Reply-To: <014db0ee-55fe-2966-a531-b8c23e97b402@web.de>
Hi Sören,
On 01/02/2023 12:35, Soeren Moch wrote:
<snip>
>>>> Obviously, if someone wants to do the vb2 conversion, then that would be
>>>> perfect. I was looking at removing analog video support, and that doesn't
>>>> look as easy as I thought it would be.
>>>>
> I only own full-featured (Nexus) cards, modified to also support a mode
> of operation like budget cards. In full-featured cards there is a
> possibility to re-read the decoded video output signal back, which could
> be similar to how analog cards work. But I never had access to
> analog/hybrid saa7146 cards, so I'm not sure I can test this mode. I
> also don't know anybody with such card who could help testing.
> I personally do not care much about analog card support in the driver,
> but will at least check which part of analog functionality is used in
> full-featured cards. Maybe the support for analog/hybrid cards and some
> test coverage comes for free with full support for full-featured cards.
It's the analog video streaming that uses vb2, so being able to test that
is critical.
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/
Regards,
Hans
next prev parent reply other threads:[~2023-02-01 13:52 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 [this message]
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
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=d9197b80-335c-ee70-eccc-ad04c026cbc9@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=abraham.manu@gmail.com \
--cc=herdler@nurfuerspam.de \
--cc=linux-media@vger.kernel.org \
--cc=smoch@web.de \
--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).