Thanks. :) I just want to learn sth about kernel driver development by this and
my driver also needs to support one interrupt in endpoint to get info reported
from the board.
----------------------------------------
> Date: Thu, 11 Jul 2013 23:34:27 -0700
> From: gre...@linuxfoundation.org
> To: unicorn_w...@outlook.com
> CC: oneu...@suse.de; linux-usb@vger.kernel.org
> Subject: Re: question on skel_read func of usb_skeleton.c
>
> On Fri, Jul 12, 2013 at 05:51:04AM +0000, WangChen wrote:
>> I'm writing a driver for OSRFX2 learning board to test bulkloop
>> read/write.
>
> What's wrong with the existing usb-serial driver that can easily do
> this?
>
>> I think non-blocking write is good for such device due to
>> the FX2 chipset has dual-buffer for bulk endpoints. I am just
>> wondering if I also need to support blocking write IO due to I used to
>> think from driver perspective, for example for the read/write
>> operations, we need to support both blocking and nonblocking by
>> default.
>
> As you control the userspace interaction to the device, you can decide
> on this, right?
>
> Also, why even write a kernel driver at all for this, why not just use
> libusb or usbfs directly from userspace?
>
> thanks,
>
> greg k-h
