From: Soeren Moch <firstname.lastname@example.org> To: Mauro Carvalho Chehab <email@example.com> Cc: Mauro Carvalho Chehab <firstname.lastname@example.org>, Greg Kroah-Hartman <email@example.com>, Andreas Regel <firstname.lastname@example.org>, Manu Abraham <email@example.com>, Oliver Endriss <firstname.lastname@example.org>, email@example.com, Eugene Syromiatnikov <firstname.lastname@example.org>, Arnd Bergmann <email@example.com> Subject: Re: [GIT PULL] SAA716x DVB driver Date: Sun, 3 Dec 2017 00:58:04 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Mauro, On 28.11.2017 19:35, Mauro Carvalho Chehab wrote: > Em Mon, 25 Sep 2017 00:17:00 +0200 > Soeren Moch <firstname.lastname@example.org> escreveu: > >>> What I'm saying is that, >>> if we're adding it on staging, we need to have a plan to reimplement >>> it to whatever API replaces the DVB video API, as this API likely >>> won't stay upstream much longer. >> AFAIK it is not usual linux policy to remove existing drivers >> with happy users and even someone who volunteered to >> maintain this. > The usual Linux policy doesn't apply to staging. The goal of staging is > to add drivers that have problems, but are fixable, and whose someone > is working to solve those issues. It is totally clear to me what staging is for. Therefore I submitted this driver for staging. I was talking about the ttpci driver. This drivers lives in drivers/media/pci/ttpci, not in staging, it implements the DVB audio/video/osd API, works great and has happy users. So the DVB video API _is already_ part of the linux userspace API. This pull request does not add anything to the already available in-kernel video API. > The staging policies include adding a TODO file describing the problems > that should be solved for the driver to be promoted. If such problems > aren't solved, the driver can be removed. Yes, of course. Therefore I added such TODO file and promised to solve these issues. > > For example, this year, we removed some lirc staging drivers because > no developers were interested (and/or had the hardware) to convert > them to use the RC core (with is a Kernel's internal API). > > In the case of saa716x, the issue is that it uses a deprecated > and undocumented userspace API, with is a way more serious issue. Unfortunately there is no other API available which provides _all_ the functionality of DVB audio/video/osd. And the TT S2-6400 hardware is developed in a way, so that it is as similar as possible to ttpci cards. In order that the vdr application can easily make use of it. So it is not surprising, that the saa716x_ff driver needs to implement the same APIs as the ttpci driver. > I'm ok to add this driver to staging if we can agree on what > should be fixed, and if someone commits to try fixing it, knowing, > in advance, that, if it doesn't get fixed on a reasonable time, it > can be removed on later Kernel versions. I already agreed on all these points. I already promised to fix whatever is necessary to get this driver out of staging, as long as the userspace API remains the same so that vdr continues to work with these cards. And once again, this API already is part of the kernel and not specific for this driver. The driver version in this pull request does not build anymore with linux-4.15-rc1. Shall I provide a new pull request with this fixed? Thanks, Soeren
next prev parent reply other threads:[~2017-12-02 23:59 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-07-16 18:34 Soeren Moch 2017-07-20 10:49 ` Mauro Carvalho Chehab 2017-07-21 20:44 ` Soeren Moch 2017-08-27 10:30 ` Mauro Carvalho Chehab 2017-09-09 12:52 ` Soeren Moch 2017-09-09 21:20 ` Mauro Carvalho Chehab 2017-09-16 12:54 ` Soeren Moch 2017-09-16 17:49 ` Mauro Carvalho Chehab 2017-09-24 22:17 ` Soeren Moch 2017-11-24 16:28 ` Tycho Lürsen 2017-11-27 11:24 ` Mauro Carvalho Chehab 2017-12-02 18:51 ` Jemma Denson 2017-12-02 19:49 ` Mauro Carvalho Chehab 2017-12-02 23:59 ` Soeren Moch 2017-12-03 10:57 ` Jemma Denson 2017-12-03 14:11 ` Soeren Moch 2017-12-03 15:04 ` Jemma Denson 2017-12-04 10:07 ` Mauro Carvalho Chehab 2018-01-19 13:59 ` Tycho Lürsen 2018-01-19 15:11 ` Jemma Denson 2018-01-20 15:49 ` Tycho Lürsen 2018-01-25 17:08 ` Jemma Denson 2017-11-28 18:35 ` [GIT PULL] " Mauro Carvalho Chehab 2017-12-02 23:58 ` Soeren Moch [this message] 2017-08-23 9:56 ` [GIT PULL RESEND] " Soeren Moch 2018-03-07 15:14 ` Mauro Carvalho Chehab
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GIT PULL] SAA716x DVB driver' \ /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
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).