EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: Linux USB serial questions
From: Andrew Gomella <andrewgomella@gmail.com>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>
Cc: "tech-talk@aps.anl.gov Talk" <tech-talk@aps.anl.gov>
Date: Thu, 18 Apr 2013 19:40:51 -0400
Thanks all for the help with figuring this out. 

I should be able to actually test having multiple devices attached to one Linux system within the next few days. I do believe all of our devices will be the 3006 variety.

To answer Andrew (Johnson)'s question, it seems it does provide a serial number attribute. When I run the "usb-devices" command I see a serial number show up for the controller. So I guess it will be feasible to have a persistent device mapping to each controller. 

For the record I am currently testing with kernel 3.2.32 

Andrew Gomella
 


On Thu, Apr 18, 2013 at 6:20 PM, J. Lewis Muir <jlmuir@imca-cat.org> wrote:
On 4/18/13 5:07 PM, Mark Rivers wrote:
> Yes, it does work for me to use modprobe with the 3006 device.  I can use either the 3000 or 3006, but not both at the same time.
>
> But if he wanted to use a mix of the 3000 and 3006 devices it would not work?

Hopefully Guy will chime in, but, without modifying the kernel, I think
a mix would require a 3.8 kernel (or newer) since the kernel would know
about the 0x104D vendor and the 0x3000 product, but would not know about
the 0x3006 product.  You could use the one available vendor-product
modprobe pair to tell the ftdi_sio module about the 0x3006 product it
doesn't know about, thus achieving the desired result of the kernel
knowing about the 0x3000 and 0x3006 devices.

Or, you could modify the kernel to tell it about the vendor and product
IDs, and then a mix should work, again assuming the ftdi_sio module at
least knows about the chip type.

Lewis


Replies:
RE: Linux USB serial questions Jim Chen
References:
Linux USB serial questions Mark Rivers
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir
Re: Linux USB serial questions Jennings Guy
Re: Linux USB serial questions J. Lewis Muir
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir

Navigate by Date:
Prev: Re: Linux USB serial questions Guy Jennings
Next: Re: autosave limitation? Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: Linux USB serial questions J. Lewis Muir
Next: RE: Linux USB serial questions Jim Chen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019