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]
Date:	Sat, 1 Nov 2008 18:55:36 +0100
From:	"Markus Rechberger" <mrechberger@...il.com>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	"Devin Heitmueller" <devin.heitmueller@...il.com>,
	"Hans Verkuil" <hverkuil@...all.nl>,
	v4l <video4linux-list@...hat.com>, linux-dvb@...uxtv.org,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	em28xx <em28xx@...ntral.de>, "Greg KH" <greg@...ah.com>,
	mchehab@...radead.org
Subject: Re: [linux-dvb] [PATCH 1/7] Adding empia base driver

On Sat, Nov 1, 2008 at 5:29 PM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> On Sat, Nov 1, 2008 at 6:19 PM, Devin Heitmueller
> <devin.heitmueller@...il.com> wrote:
>> The reality is that from a technical standpoint I really want Markus
>> to be the maintainer.  He knows more about the devices than anyone,
>> works for the vendor, and has access to all the datasheets.  That
>> said, I don't want a situation where he is the *only* one who can do
>> work on the codebase because it is poorly commented and structured in
>> a way where only he can understand why it works the way it does.
>> Also, I believe certain design decisions should be made as a result of
>> consensus with the other maintainers, taking into consideration
>> consistency across drivers.
>
> I can understand that you want him to be the maintainer. But so far he
> hasn't really shown to be interested in doing that. It's just bit sad
> that the we don't have a proper driver given that the code exists and
> that there's a person who's willing to do the work to get it merged...
>

There's alot discussion and I haven't followed it yet although, the
best way to go
seen from my side is to take the em28xx-new code and merge the usable kernelcode
into that one (note that only ~10% of the devices in the kernel em28xx
driver are actually
tested).

I read about the License, I can say this is no issue overall, all of
the code is available under GPL,
and some of it is also under BSD license.

I need to catch up the other mails before continuing...

Markus
--
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