linux-kernel - Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

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: <470D61CF.3070307@redhat.com>
Date:	Wed, 10 Oct 2007 19:35:43 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Markus Rechberger <mrechberger@...il.com>
CC:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.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

On 10/10/2007 07:24 PM, Markus Rechberger wrote:
> 
> To point to more changes within the available driver which hasn't been merged
> within the last 1 1/2 years:
> * it supports non usbaudio based video devices.
> * has support for dvb-t/atsc
> * allows multiple device node access in case of analogue TV
> * has teletext/VBI support for PAL.
> * it supports modules which are now in userspace instead of
> kernelspace due disagreements with some developers for 1 1/2 years.
> * I do not agree with certain developers who do not have any experience
> with certain parts of the code for redoing it a 4th time now. My patience
> is over, which includes the company support in my back to get those
> devices supported.
> 

Do you plan on maintaining your own private driver tree for all of eternity?
-
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/