linux-kernel - Re: Free Linux Driver Development!

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:	04 Feb 2007 14:29:13 +0100
From:	Christer Weinigel <christer@...nigel.se>
To:	Greg KH <greg@...ah.com>
Cc:	Andrew Lyon <andrew.lyon@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

Greg KH <greg@...ah.com> writes:

> Why would a userspace driver not work out for this.  We already can
> saturate the USB bus with a userspace program

That is unfortunately not quite true.  I have a (unfortunately
proprietary) driver for a USB device that simply cannot be implemented
in userspace.  The USB device is a measurement device that pushes
close to 800 kBytes/second of data through a FT245 chip.  The
measurement device does no flow control at all, it just presents a
sample every 125 us to the FT245 and with only 256 bytes of buffer in
the FT245 the only way to handle that is to have two URBs in flight at
the same time, and I haven't found any way to do that in a robust and
non-racey way from userspace.  So the comment "The USB subsystem has
changed a lot over time, and it has been possible to create userspace
USB drivers using usbfs/libusb/gadgetfs that operate as fast as the
USB bus allows." from feature-removal-schedule.txt is wrong I
think. :-(

Personally I'd much prefer to release the driver as open source, but
as a consultant you don't get to decide what the customer does.  So
now they sit there with a driver that warns them that it'll stop
working after february 2008.

On a different topic, my personal pet peeve is USB scanners.  There
seems to be just a handful of different manufacturers of chips used in
USB scanners: Realtek and Genesys covers 90% of the scanners.  The
SANE team has done a wonderful job of reverse engineering a lot of
scanners, but the models change so fast that there seems to be no
chance of keeping up.  If the chip manufacturers just released specs
for their chips and the scanner manufacturers could then document what
settings to use Linux could have support for almost all USB scanners
on the market, and it would probably cost them very little to do that.
If I could find a good (4800-9600 dpi) scanner which said "supported
by SANE" on the box I'd buy it immedately.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Christer Weinigel <christer@...nigel.se>  http://www.weinigel.se
-
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/