Re: Mapping USB-ports "by slot" rather than by "usb attributes"

ique udev-rule. Looking forward to a reply :) Thanks and Regards, Ajay On Tue, Sep 13, 2016 at 7:34 PM, Greg KH <gre...@linuxfoundation.org> wrote: > On Tue, Sep 13, 2016 at 07:20:01PM +0530, Ajay Garg wrote: >> A. (sorry for my stupid realisation-originated-question), for

Re: Mapping USB-ports "by slot" rather than by "usb attributes"

s, thanks a ton Greg and Felipe for your prompt responses !!! Thanks and Regards, Ajay On Tue, Sep 13, 2016 at 11:30 AM, Felipe Balbi <felipe.ba...@linux.intel.com> wrote: > > Hi, > > Ajay Garg <ajaygargn...@gmail.com> writes: >> Hi All. >> >> Till now, we

Mapping USB-ports "by slot" rather than by "usb attributes"

Hi All. Till now, we had a single usb-serial-cable, that we needed to associate to a static tty-name. http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/ worked perfect for our purpose (till now). However, we now require that multiple "identical" usb-serial-cables be inserted

Re: Queries regrading USB-driver software-architecture

a) *could* be skipped, but I have a bit of time-constraint, so will stick to the two-step formula :P Thanks again to everyone for the help !!! Thanks and Regards, Ajay On Mon, Aug 29, 2016 at 6:38 PM, Greg KH <gre...@linuxfoundation.org> wrote: > On Mon, Aug 29, 2016 at 06:26:30PM +0530,

Re: Queries regrading USB-driver software-architecture

gre...@linuxfoundation.org> wrote: > On Mon, Aug 29, 2016 at 05:56:03PM +0530, Ajay Garg wrote: >> Hi All. >> >> We have a PC-in-a-box unit, with 2 COM-ports, 2 USB 2.0 ports and 1 >> USB 3.0 port. >> We are testing the COM-ports (COM1 and COM2) and the USB-ports. >> >>

Queries regrading USB-driver software-architecture

Hi All. We have a PC-in-a-box unit, with 2 COM-ports, 2 USB 2.0 ports and 1 USB 3.0 port. We are testing the COM-ports (COM1 and COM2) and the USB-ports. We proceeded as follows :: a) In the setup User-App <=> COM1 <=> RS232-data <=> RS232-to-RS485 converter <=> RS485-data <=> Modbus-Device

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

Ok Greg :) On Tue, Aug 9, 2016 at 1:44 PM, Greg KH <gre...@linuxfoundation.org> wrote: > On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote: >> Hi All. >> >> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's >> MC8090 modem, and we h

Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

Hi All. We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's MC8090 modem, and we have a requirement wherein we need to have access to the modem-serial-port (from our user-application that is). Right now, we see that /usr/sbin/ModemManager is always connected to /dev/ttyUSB3 (which

Re: Likely issue with ch341 kernel-module/driver

### Completely lost :( On Wed, Aug 26, 2015 at 11:45 PM, Johan Hovold jo...@kernel.org wrote: On Wed, Aug 26, 2015 at 08:09:30PM +0200, Peter Stuge wrote: Johan Hovold wrote: On Wed, Aug 26, 2015 at 09:39:36PM +0530, Ajay Garg wrote: .. garbage

Re: Likely issue with ch341 kernel-module/driver

Hi John. On Thu, Aug 27, 2015 at 1:07 PM, Johan Hovold jo...@kernel.org wrote: Try to see if you can get the device to work reliably with some other driver (vendor driver or other OS) to rule out a broken device. I tested the serial-usb adapter using a loopback-hardware-tool (confirmed to be