Please keep linux-usb on CC.
On Wed, Jan 10, 2018 at 10:01:40AM +0100, Max Schulze wrote:
>
> > Yeah, that's not a CDC device so usb-serial is the right subsystem for
> > this one.
> >
> >>> Yeah, this is expected since you will not be able to do modem control
> >>> when using the generic driver.
On Mon, Jan 08, 2018 at 07:56:51PM +0100, Max Schulze wrote:
> Thanks Johan for taking a look.
>
>
> Am 08.01.2018 um 17:30 schrieb Johan Hovold:
> > Adding the device ids and a quirk to cdc_acm.c
> >>> .driver_info = NO_UNION_NORMAL,
> >> does only suppress the "Zero length" message.
> > Do you
Thanks Johan for taking a look.
Am 08.01.2018 um 17:30 schrieb Johan Hovold:
> Adding the device ids and a quirk to cdc_acm.c
>>> .driver_info = NO_UNION_NORMAL,
>> does only suppress the "Zero length" message.
> Do you then get a ttyACMn device? Or some other error?
Nothing more. No ttyACM devic
On Thu, Jan 04, 2018 at 07:38:26PM +0100, Max Schulze wrote:
> Hello,
>
> I need some advice how to debug a device, that under Windows presents 2
> virtual com ports. Windows .sys. file mentions a "Jungo CDC ACM OBEX
> Driver".
>
>
> I get the following dmesg output
>
> > [ 1700.263981] usb 1-1
Hello,
I need some advice how to debug a device, that under Windows presents 2
virtual com ports. Windows .sys. file mentions a "Jungo CDC ACM OBEX
Driver".
I get the following dmesg output
> [ 1700.263981] usb 1-1.4: new full-speed USB device number 10 using
> ehci-pci
> [ 1700.378186] usb 1-1
