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  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:	Fri, 5 Feb 2010 16:26:42 -0800
From:	"Chris Verges" <>
To:	"Greg KH" <>
Cc:	<>, <>,
	"Rob Owings" <>
Subject: RE: [PATCH] linux-2.6.32-directemp

> Sorry, but no, this driver will not be accepted, as it can be done
> fine from userspace instead of a kernel driver, as discussed before.

Hi Greg,

Sounds good.  I'll still be sending out an updated patch for anyone who
is interested in a kernel driver.  They're welcome to patch in the
driver themselves.

I may be missing some key piece of information about libusb and usbfs,
but it seems like it pushes a lot of the protocol communication off to
the user app.  So if there are several user apps that want to use the
same USB device, they either need a userland library or to re-implement
functionality; is that correct?

What I may be missing is the rationale behind pushing these drivers into
userland libraries and having yet another entity in the FOSS world that
is responsible for managing them.  The kernel seems like an obvious
clearinghouse for software/hardware interactions.  Yes, there may be
lots of drivers, but at least everyone knows where to go for them.  But
like I said before, I may be missing something.

Thanks for the tips about libusb/usbfs!

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists