From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: tw686x driver
Date: Thu, 3 Mar 2016 15:39:35 +0100 [thread overview]
Message-ID: <56D84CA7.4050800@xs4all.nl> (raw)
In-Reply-To: <m3h9gnod3t.fsf@t19.piap.pl>
On 03/03/16 15:22, Krzysztof Hałasa wrote:
> Hans Verkuil <hverkuil@xs4all.nl> writes:
>
>> There is no point whatsoever in committing a driver and then replacing it
>> with another which has a different feature set. I'm not going to do
>> that.
>
> Sure, that's why I haven't asked you to do it.
> Now there is no another driver, as Ezequiel stated - there is just one
> driver.
>
> The point is clear, showing who exactly wrote what.
>
>> One option that might be much more interesting is to add your driver to
>> staging with a TODO stating that the field support should be added to
>> the mainline driver.
>
> Field mode is one thing. What's a bit more important is that Ezequiel's
> changes take away the SG DMA, and basically all DMA. The chip has to use
> DMA, but his driver then simply memcpy() all the data to userspace
> buffers. This doesn't work on low-power machines.
>
> Staging is meant for completely different situation - for immature,
> incomplete code. It has nothing to do with the case.
It can be for anything that prevents it from being mainlined. It was (still is?)
used for mature android drivers, for example.
>
>> I'm not sure if Mauro would go for it, but I think this is a fair option.
>
> I don't expect the situation to be fair to me, anymore.
>
> I also don't want to pursue the legal stuff, copyright laws etc.,
> but a quick glance at the COPYING file at the root of the kernel sources
> may be helpful:
>
>> 2. You may modify your copy or copies of the Program or any portion
>> of it, thus forming a work based on the Program, and copy and
>> distribute such modifications or work under the terms of Section 1
>> above, provided that you also meet all of these conditions:
>>
>> a) You must cause the modified files to carry prominent notices
>> stating that you changed the files and the date of any change.
>
> I don't even ask for that much - I only ask that the single set of
> changes from Ezequiel has this very information. This is BTW one of the
> reasons we switched to git.
Ezequiel, can you make a v4 and add a link to the original patch posted by
Krzysztof that you based your code on?
I think that takes care of the provenance.
Regards,
Hans
next prev parent reply other threads:[~2016-03-03 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 8:32 tw686x driver Hans Verkuil
2016-03-03 6:51 ` Krzysztof Hałasa
2016-03-03 7:32 ` Hans Verkuil
2016-03-03 12:41 ` Krzysztof Hałasa
2016-03-03 13:37 ` Hans Verkuil
2016-03-03 14:22 ` Krzysztof Hałasa
2016-03-03 14:39 ` Hans Verkuil [this message]
2016-03-04 6:11 ` Krzysztof Hałasa
2016-03-04 11:11 ` Hans Verkuil
2016-03-04 12:37 ` Krzysztof Hałasa
2016-03-04 13:40 ` Hans Verkuil
2016-03-07 6:41 ` Krzysztof Hałasa
2016-03-10 7:16 ` Krzysztof Hałasa
2016-03-10 7:24 ` Hans Verkuil
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=56D84CA7.4050800@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=khalasa@piap.pl \
--cc=linux-media@vger.kernel.org \
/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