Hi,
I have tried the usb->serial adapters I could find lying around the office.
Using the code you sent me, not the very latest from sources.
The FTDI chips we use in our products work fine
ep13.0 255 csp 0xff vid 0x10c4 did 0xea60 'Silicon Labs' 'CP2102
USB to UART Bridge Controlle
> Maybe it's as simple
> as having separate read and write QLocks.
For normal endpoints it is that simple. Control endpoints, however,
are bidirectional but effectively half-duplex, so reads and writes
still need to be locked against each other.
Today's version of /n/sources/contrib/miller/9/bcm
On Mon, Dec 12, 2016 at 9:39 PM, Richard Miller <9f...@hamnavoe.com> wrote:
> Oops, pressed the wrong button - that reply was intended for
> Steve Simon and not the whole of 9fans. Oh well, if anybody
> else wants to rummage through the usbdwc driver too, they
> are welcome.
>
Thanks, because I
Oops, pressed the wrong button - that reply was intended for
Steve Simon and not the whole of 9fans. Oh well, if anybody
else wants to rummage through the usbdwc driver too, they
are welcome.
> I cannot get the usb serial interfaces we use to work. I have never managed
> to get
> usb serial adapters to work with the raspberry pi, though never had problems
> on x86 boxen.
> ...
>
> Text into the pi works fine, but outgoing text seems stalled until text is
> received,
> I can type ahe
Hi,
I have upgraded my pi desktop to a 3 which is noticable faster.
I am using Richard's pi image which as usual works perfectly, but for one
wrinkle.
I cannot get the usb serial interfaces we use to work. I have never managed to
get
usb serial adapters to work with the raspberry pi, though nev
