[linux-usb-devel] Re: HIDDEV larger request buffer

2006-04-10 Thread Greg KH
On Mon, Apr 10, 2006 at 03:08:50PM -0600, Michael Downey wrote: > I am currently looking at using a MegTek USB insertion reader and I have > run into a problem with the current hiddev. The card reader returns a > 338 byte Input report on the interrupt in channel everytime a card is > inserted. Th

[linux-usb-devel] Re: HIDDEV larger request buffer

2006-04-11 Thread Vojtech Pavlik
On Mon, Apr 10, 2006 at 05:03:21PM -0700, Greg KH wrote: > On Mon, Apr 10, 2006 at 03:08:50PM -0600, Michael Downey wrote: > > I am currently looking at using a MegTek USB insertion reader and I have > > run into a problem with the current hiddev. The card reader returns a > > 338 byte Input repo

Re: [linux-usb-devel] Re: HIDDEV larger request buffer

2006-04-11 Thread Michael Downey
Vojtech Pavlik wrote: >On Mon, Apr 10, 2006 at 05:03:21PM -0700, Greg KH wrote: > > > >>On Mon, Apr 10, 2006 at 03:08:50PM -0600, Michael Downey wrote: >> >> >>>I am currently looking at using a MegTek USB insertion reader and I have >>>run into a problem with the current hiddev. The card r

Re: [linux-usb-devel] Re: HIDDEV larger request buffer

2006-04-11 Thread Vojtech Pavlik
On Tue, Apr 11, 2006 at 08:52:17AM -0600, Michael Downey wrote: > >The reason is that it was originally intended for devices which don't > >issue huge numbers of reports in one go, and 64 was supposed to be > >'large enough' for userspace to be able to empty the buffers as the data > >are coming f

Re: [linux-usb-devel] Re: HIDDEV larger request buffer

2006-04-11 Thread Michael Downey
Vojtech Pavlik wrote: >On Tue, Apr 11, 2006 at 08:52:17AM -0600, Michael Downey wrote: > > > >>>The reason is that it was originally intended for devices which don't >>>issue huge numbers of reports in one go, and 64 was supposed to be >>>'large enough' for userspace to be able to empty the buff