Hi,
I finally found some time to dig into the ftdi eeprom handling.
On Tue, Jun 26, 2018 at 02:54:48PM +0200, Loic Poulain wrote:
> Most of FTDI's devices have an EEPROM which records FTDI devices
> configuration setting (e.g. the VID, PID, I/O config...) and user
> data. For example, FT232R and
On Mon, 9 Jul 2018, R0b0t1 wrote:
> > As far as I can tell, all the transfers did complete properly. I
> > didn't find any where the completion line contained an error code.
> >
>
> Is anyone able to comment on this in more detail? I thought it was
> supposed to be reported if a transfer did not
Hi Felipe,
2018-06-27 14:30 GMT+02:00 Felipe Balbi :
>
> looks like we need to do away with the wait_event_lock_irq()
> call. usb_ep_dequeue() can be called from within the controller's
> interrupt handler, so we can't rely on wait_event_lock_irq(). I guess
> the best thing here would be to mark T
On Tue, 10 Jul 2018, Paul Elder wrote:
> > > Are there other mechanisms ? If there are no other
> > > mechanism, I won't be able to validate the DATA stage in userspace as I
> > > can
> > > only send the data to userspace in the DATA stage request completion
> > > handler,
> > > and have to t
Top of the day to you, this is in respect of a very beneficial transaction
which you would not want to let go reply for more details,
Regards,
Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Jul 10, 2018 at 11:23:50AM -0400, Alan Stern wrote:
> On Tue, 10 Jul 2018, Paul Elder wrote:
>
> > > > Are there other mechanisms ? If there are no other
> > > > mechanism, I won't be able to validate the DATA stage in userspace as I
> > > > can
> > > > only send the data to userspace i
