From: Stefan Herdler <herdler@nurfuerspam.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org,
Manu Abraham <abraham.manu@gmail.com>,
Tomasz Maciej Nowak <tmn505@gmail.com>,
Corinna Vinschen <vinschen@redhat.com>,
Soeren Moch <smoch@web.de>
Subject: Re: Future of the SAA7146 drivers
Date: Mon, 13 Feb 2023 00:10:29 +0100 [thread overview]
Message-ID: <99397771-409b-e487-e429-d5c9feb82209@nurfuerspam.de> (raw)
In-Reply-To: <20230208100847.3ec87576@coco.lan>
On 08/02/23 10:08, Mauro Carvalho Chehab wrote:
[...]
>>> 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).
Hi Mauro,
that sounds like a good plan to me.
Documentation is a solvable problem. At least for the parts used by the
full-featured-cards.
The VDR-plugin-API is pretty well documented (1) and the output-plugin
for the full-featured-cards push most commands right trough.
It is still a laborious task to crosscheck the documents, but most
information should be already there.
I think I'll get it done, but it my take a while depending on my other
duties.
Documenting the "unused" parts could be difficult.
There is no helpful documentation about the "enigma2" receivers. At
least I haven't found some.
This receivers are also not completely open source. The the drivers seem
to be binary only.
The only things I know for sure are: The OSD-part of the DVB-API isn't
used (2) and the audio- and video-part are used (3).
I manged to find the file where the headers are included (4), but there
is no documentation either.
I think I'll start with the used parts and see how far I come.
I'll mail again when I'm done, probably in 2 or 3 weeks.
Thanks and Regards
Stefan
>
>> (* 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
1. http://git.tvdr.de/?p=vdr.git;a=blob;f=device.h
2. https://en.wikipedia.org/wiki/Enigma_(DVB)#Technical_realization
"direct access to framebuffer"
3.
https://github.com/OpenPLi/openpli-oe-core/blob/10e1dd6b0109ce787dbae204275659778119eafb/meta-openpli/recipes-kernel/linux-libc-headers/linux-libc-headers/audio_video_ioctl.patch
4. https://github.com/openatv/enigma2/blob/master/lib/dvb/decoder.cpp
next prev parent reply other threads:[~2023-02-12 23:10 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
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 [this message]
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=99397771-409b-e487-e429-d5c9feb82209@nurfuerspam.de \
--to=herdler@nurfuerspam.de \
--cc=abraham.manu@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).