On 06/25/2013 11:17 AM, Alan Stern wrote:
Say the sensor A gets
to port 3 and sensor B gets to port 4 the first time, but when a reset
happens they get switched in order and sensor A gets to port 5 and
sensor B gets to port 4??.
That won't happen unless you remove the wires connecting the senso
On 06/25/2013 01:29 PM, Greg KH wrote:
Then that library should somehow be unbinding the device from the ttyUSB
port, right? I really don't know how that library works, sorry.
Now that I checked, it does, you're right. The libftdi userspace
library does remove the entries from /dev.
AFAIK mde
On 06/25/2013 11:42 AM, Greg KH wrote:
On Tue, Jun 25, 2013 at 09:25:50AM -0400, raespi wrote:
Hi ... I'm using an ARM Samsung S3C24XX processor with a 3.1.10
kernel.
Note, this is a very old and unsupported kernel version, you really
should consider upgrading, or getting support for
On 06/25/2013 10:26 AM, Alan Stern wrote:
On Tue, 25 Jun 2013, raespi wrote:
On my board I can't hook up my application again to the new address
since it's the only parameter identifiable by it. Both FTDI Devices
have the same product and vendor numbers:
Bus 001 Device 003: ID 040
Hi ... I'm using an ARM Samsung S3C24XX processor with a 3.1.10 kernel.
I'm interested in creating medical equipment using Linux and came onto
an issue today. I've created an application that connects to two FTDI
devices and reads continuous data from a medical sensor. I have a
custom based
