Re: rtl2832u support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday, October 19, 2010 21:26:13 Devin Heitmueller wrote:
> On Tue, Oct 19, 2010 at 1:42 PM, Damjan Marion <damjan.marion@xxxxxxxxx> 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.

Them's the rules for kernel development.

I've done my share of coding style cleanups. I never understand why people
dislike doing that. In my experience it always greatly improves the code
(i.e. I can actually understand it) and it tends to highlight the remaining
problematic areas in the driver.

Of course, I can also rant for several paragraphs about companies throwing
code over the wall without bothering to actually do the remaining work to
get it mainlined. The very least they can do is to sponsor someone to do the
work for them.

But I'll spare you that :-)

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux