linux-kernel - Re: [2.6 patch] remove the broken VIDEO

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: <1164707859.12613.7.camel@localhost>
Date:	Tue, 28 Nov 2006 07:57:39 -0200
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	jfeise@...se.com
Cc:	Adrian Bunk <bunk@...sta.de>,
	Linux and Kernel Video <video4linux-list@...hat.com>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Pauline Middelink <middelink@...yware.nl>
Subject: Re: [2.6 patch] remove the broken VIDEO_ZR36120 driver

Hi Joe,

Em Seg, 2006-11-27 às 22:36 -0800, Joe Feise escreveu:
> Adrian Bunk wrote on 11/27/06 22:07:
> 
> > On Mon, Nov 27, 2006 at 09:30:27PM -0800, Joe Feise wrote:
> >> Adrian Bunk wrote on 11/25/06 11:15:
> >>
> >>> But if anyone wants to ever revive this driver, the code is still 
> >>> present in the older kernel releases.
> >> Hmm, there are people out there (like me) who still use it and have patched it
> >> to get it working on 2.6.x.
> > If you anyway have to patch your kernel, you can as well patch the 
> > complete driver into the kernel.
> Well, there are other things outside the actual driver code that may change, and
> that would make it harder to keep my patch in sync.
Keeping it in sync is not hard. Most changes are just small API changes
that are easy to port to all drivers, since they all behave likely.
Also, when kernel hackers changes API, they usually send patches fixing
API also at the affected drivers (of course for not-broken stuff).
> And actually, I submitted my patch some time ago to the maintainer of the driver
> (Pauline Middelink.)  Unfortunately, it never made it into the kernel, nor did I
> get any feedback from her. I have no idea if she is still active (she is listed
> as maintainer at least until 2.6.17.) I cc'ed her on this mail.
If you are interested on fixing this driver, you may submit the fix
patch to me, with your SOB. I'm maintaining the V4L subsystem as a hole.
> 
> 
> -Joe
> 
> 
Cheers, 
Mauro.

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