From: Soeren Moch <firstname.lastname@example.org>
To: Mauro Carvalho Chehab <email@example.com>,
Jemma Denson <firstname.lastname@example.org>
Cc: "Tycho Lürsen" <email@example.com>,
"Mauro Carvalho Chehab" <firstname.lastname@example.org>,
Subject: Re: [GIT PULL] SAA716x DVB driver
Date: Sun, 3 Dec 2017 00:59:20 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 02.12.2017 20:49, Mauro Carvalho Chehab wrote:
> Em Sat, 2 Dec 2017 18:51:16 +0000
> Jemma Denson <firstname.lastname@example.org> escreveu:
>> Hi Mauro,
>> On 27/11/17 11:24, Mauro Carvalho Chehab wrote:
>>> Em Fri, 24 Nov 2017 17:28:37 +0100
>>> Tycho Lürsen <email@example.com> escreveu:
>>>> Hi Mauro,
>>>> afaik the last communication about submission of this driver was about
>>>> two months ago.
>>>> This driver is important to me, because I own several TurboSight cards
>>>> that are saa716x based. I want to submit a patch that supports my cards.
>>>> Of course I can only do so when you accept this driver in the first place.
>>>> Any chance you and Sören agree about how to proceed about this driver
>>>> anytime soon?
>>> If we can reach an agreement about what should be done for the driver
>>> to be promoted from staging some day, I'll merge it. Otherwise,
>>> it can be kept maintained out of tree. This driver has been maintained
>>> OOT for a very long time, and it seems that people were happy with
>>> that, as only at the second half of this year someone is requesting
>>> to merge it.
>>> So, while I agree that the best is to merge it upstream and
>>> address the issues that made it OOT for a long time, we shouldn't
>>> rush it with the risk of doing more harm than good.
>> Would I be correct in thinking the main blocker to this is the *_ff features
>> used by the S2-6400 card? There's plenty of other cards using this chipset
>> that don't need that part.
>> Would a solution for now to be a driver with the ff components stripped out,
>> and then the ff API work can be done later when / if there's any interest?
> Works for me. In such case (and provided that the driver without *_ff are
> in good shape), we could merge it under drivers/media (instead of merging
> it on staging).
All the entries in the TODO file are not specific for saa716x_ff.
>> I guess a problem would be finding a maintainer, I'm happy to put together
>> a stripped down driver just supporting the TBS card I use (I already have
>> one I use with dkms), but I'm not sure I have the time or knowledge of this
>> chipset to be a maintainer.
There is chipset specific stuff to fix, especially irq handling.
> As we're talking more about touching at uAPI, probably it doesn't require
> chipsed knowledge. Only time and interest on doing it.
> Please sync with Soeren. Perhaps if you both could help on it, it would
> make the task easier.
As I already wrote to different people off-list: I'm happy to support
more cards with the saa7160 bridge and maintain these in this driver. As
hobbyist programmer this of course makes no sense to me, if the hardware
I own (S2-6400) is not supported.
>> Unfortunately my workplace is phasing out
>> these cards otherwise I'd try and get them to sponsor me rather than do it
>> on my own time!
> Yeah, getting sponsored to do it would make things easier.
next prev parent reply other threads:[~2017-12-03 0:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 18:34 [GIT PULL] SAA716x DVB driver 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 [this message]
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
2017-08-23 9:56 ` [GIT PULL RESEND] " Soeren Moch
2018-03-07 15:14 ` Mauro Carvalho Chehab
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).