lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <470E23A0.5050500@aurel32.net>
Date:	Thu, 11 Oct 2007 15:22:40 +0200
From:	Aurelien Jarno <aurelien@...el32.net>
To:	Markus Rechberger <mrechberger@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	linux-dvb-maintainer@...uxtv.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	video4linux-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

Markus Rechberger a écrit :
> On 10/11/07, Aurelien Jarno <aurelien@...el32.net> wrote:
>> Markus Rechberger a écrit :
>>> On 10/11/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>>> As such, the old and decrepit em28xx driver seems more useful to people,
>>>> since at least it supports the limited set of hardware on its own.
>>> it does not since it's broken and feature limited. On the other side
>> I have a device which works perfectly with it if you add the vendor and
>> product ID to the list. I don't really call that broken. And it doesn't
>> need a firmware.
>>
> 
> Aurelien,
> 
> the device you're using is around 2 years old. You're one of the lucky
> ones, I have tonns of support mails in my mail account from people who
> own almost a similar device but with different videodecoders which are
> not fully supported in the kernel or which worked and got broken
> during the time.
> It took me around 4 hours to debug such an issue last years remotly
> with an enduser (which includes that noone cared to ask me if I'm fine
> with such an update, neither did someone ask people who own such
> devices that they should test the changes).
> Please also take other devices and upcoming devices into account,
> since i'm willing to spend that time and since I'm in contact with
> various companies who provide several components of those devices.
> 

I agree I am lucky, but the fact is that the in-kernel driver supports
*some* devices, and *works* correctly for them. On the other side, your
driver supports more devices, but it is and *out-of-tree* driver.

Please either work to get your change merged, or stop complaining about
changes done to the in-kernel driver.

Moreover if you get a closer look at v4l-dvb git, you will see that the
changes proposed by Mauro are not em28xx specific, and is actually the
same change done on a lot of of v4l/dvb drivers.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@...ian.org         | aurelien@...el32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ