linux-kernel - Re: [GIT PATCH] USB fixes for 2.6.26-rc4

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:	Thu, 29 May 2008 14:47:06 -0700
From:	Greg KH <gregkh@...e.de>
To:	Laurent Pinchart <laurent.pinchart@...net.be>,
	Matthew Garrett <mjg@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [GIT PATCH] USB fixes for 2.6.26-rc4

On Thu, May 29, 2008 at 11:27:45PM +0200, Laurent Pinchart wrote:
> Hi Greg,
> 
> On Thursday 29 May 2008, Greg KH wrote:
> > Matthew Garrett (1):
> >       USB: Firmware loader driver for USB Apple iSight camera
> 
> Sorry not to have spotted this sooner, but I don't like this one. Why do we 
> need a specific kernel driver when a userspace tool (fxload) exists to 
> perform the same task, especially when the tool handles udev integration 
> nicely ? The Apple iSight uses an EZ-USB chipset. If we really want a kernel 
> driver for that it should probably be made more generic to handle all 
> EZ-USB-based devices.

Well, perhaps because no one did this kind of integration before?  :)

I'll take this driver out later, if the infrastructure is put into
place, and some kind of driver package is created for the distros to use
to implement this.

But until then, the easiest way to get this hardware working for users
is a tiny kernel firmware loader just like this one.  If you think we
should turn it into something for all ezusb devices, that's also a
possiblity.

thanks,

greg k-h
--
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/