> > > So, to get the ball rolling, here are some factors that IMHO
> > > help decide in which side to implement a driver:
> > >
> > > - if the driver ties a hardware device to an existing
> > >in-kernel interface (network, block, serial, bluetooth,
> > >video4linux, etc.), it should probab
On Thu, Jan 03, 2008 at 03:08:55PM -0800, mgross wrote:
> On Wed, Jan 02, 2008 at 07:59:15PM +, Paulo Marques wrote:
> > Xiaofan Chen wrote:
> >> On Dec 30, 2007 11:53 AM, mgross <[EMAIL PROTECTED]> wrote:
> >>> [...]
> >>> What is the linux-usb policies on new drivers that could be
> >>> imple
On Wed, Jan 02, 2008 at 07:59:15PM +, Paulo Marques wrote:
> Xiaofan Chen wrote:
>> On Dec 30, 2007 11:53 AM, mgross <[EMAIL PROTECTED]> wrote:
>>> [...]
>>> What is the linux-usb policies on new drivers that could be
>>> implemented in user space? When does a kernel driver make sense over
>>>
Xiaofan Chen wrote:
On Dec 30, 2007 11:53 AM, mgross <[EMAIL PROTECTED]> wrote:
[...]
What is the linux-usb policies on new drivers that could be
implemented in user space? When does a kernel driver make sense over
a libusb one?
That would be interesting to know.
I myself have been faced wi
