Thank you a lot for the assistance and thanks for the link to the
discussion.

I'v understood that it is definitely not a problem in libftdi, but it's bug
in kernel or in the chip itself. I will investigate the question more
thoroughly.

Best regards,
Alexey Kosilin

On Sun, Jun 26, 2011 at 4:15 PM, Xiaofan Chen <[email protected]> wrote:

> On Sun, Jun 26, 2011 at 7:58 PM, Xiaofan Chen <[email protected]> wrote:
> > On Sun, Jun 26, 2011 at 7:55 PM, Xiaofan Chen <[email protected]>
> wrote:
> >>      Endpoint Descriptor:
> >>        bLength                 7
> >>        bDescriptorType         5
> >>        bEndpointAddress     0x81  EP 1 IN
> >>        bmAttributes            2
> >>          Transfer Type            Bulk
> >>          Synch Type               None
> >>          Usage Type               Data
> >>        wMaxPacketSize     0x0000  1x 0 bytes
> >>        bInterval               0
> >>      Endpoint Descriptor:
> >>        bLength                 7
> >>        bDescriptorType         5
> >>        bEndpointAddress     0x02  EP 2 OUT
> >>        bmAttributes            2
> >>          Transfer Type            Bulk
> >>          Synch Type               None
> >>          Usage Type               Data
> >>        wMaxPacketSize     0x0040  1x 64 bytes
> >>        bInterval               0
> >>
> > Oops, my bad, something is wrong with your device that
> > wMaxPacketSize for EP1 IN is zero. In that case, how
> > can it send data to the host?
> >
> > What is your system?
> >
>
> I search my Linux USB mailing list and indeed this is
> possible. The fix should be in the kernel and not in the
> user space (libftdi).
>
> Discussion:
> http://marc.info/?t=120423246300011&r=1&w=2
>
> Somehow I do not see the patch submitted later
> in the list.
>
>
> --
> Xiaofan
>
> --
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
> To unsubscribe send a mail to [email protected]
>
>


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to [email protected]   

Reply via email to