From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Damjan Marion <dmarion@me.com>
Cc: linux-media@vger.kernel.org
Subject: Re: rtl2832u support
Date: Fri, 19 Nov 2010 09:36:40 +0200 [thread overview]
Message-ID: <1290152200.9749.1.camel@maxim-laptop> (raw)
In-Reply-To: <C5D61175-5018-4D8F-B7D2-4A7FB5174DFB@me.com>
On Wed, 2010-11-17 at 12:15 +0100, Damjan Marion wrote:
> On Oct 19, 2010, at 10:27 PM, Hans Verkuil wrote:
> > On Tuesday, October 19, 2010 21:26:13 Devin Heitmueller wrote:
> >> On Tue, Oct 19, 2010 at 1:42 PM, Damjan Marion <damjan.marion@gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> Is there any special reason why driver for rtl2832u DVB-T receiver chipset is not included into v4l-dvb?
> >>>
> >>> Realtek published source code under GPL:
> >>>
> >>> MODULE_AUTHOR("Realtek");
> >>> MODULE_DESCRIPTION("Driver for the RTL2832U DVB-T / RTL2836 DTMB USB2.0 device");
> >>> MODULE_VERSION("1.4.2");
> >>> MODULE_LICENSE("GPL");
> >>
> >> Unfortunately, in most cases much more is "required" than having a
> >> working driver under the GPL in order for it to be accepted upstream.
> >> In some cases it can mean a developer spending a few hours cleaning up
> >> whitespace and indentation, and in other cases it means significant
> >> work to the driver is required.
> >>
> >> The position the LinuxTV team has taken is that they would rather have
> >> no upstream driver at all than to have a driver which doesn't have the
> >> right indentation or other aesthetic problems which has no bearing on
> >> how well the driver actually works.
> >>
> >> This is one of the big reasons KernelLabs has tens of thousands of
> >> lines of code adding support for a variety of devices with many happy
> >> users (who are willing to go through the trouble to compile from
> >> source), but the code cannot be accepted upstream. I just cannot find
> >> the time to do the "idiot work".
> >
> > Bullshit. First of all these rules are those of the kernel community
> > as a whole and *not* linuxtv as such, and secondly you can upstream such
> > drivers in the staging tree. If you want to move it out of staging, then
> > it will take indeed more work since the quality requirements are higher
> > there.
>
>
> Do we have a common agreement that this driver can go to staging as-is?
>
> If yes, I have patch ready, just need to know where to send it (It is around 1 MB).
I also bought that device few days ago.
Needless to say it works perfectly (better that in windows) with this
driver.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-11-19 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 17:42 rtl2832u support Damjan Marion
2010-10-19 19:10 ` Antti Palosaari
2010-10-19 19:33 ` Damjan Marion
2010-10-19 19:41 ` Antti Palosaari
2010-11-02 12:05 ` poma
2010-10-19 19:26 ` Devin Heitmueller
2010-10-19 20:27 ` Hans Verkuil
2010-10-19 20:47 ` Alex Deucher
2010-10-19 21:28 ` Devin Heitmueller
2010-10-20 6:44 ` Hans Verkuil
2010-11-17 11:15 ` Damjan Marion
2010-11-19 7:36 ` Maxim Levitsky [this message]
2010-11-20 22:37 ` Maxim Levitsky
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=1290152200.9749.1.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=dmarion@me.com \
--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