linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Markus Breunig <Markus.L.Breunig@gmx.net>
Cc: Johan Hovold <johan@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Subject: Re: Fwd: Re: New USB Device
Date: Tue, 13 Aug 2019 11:37:07 +0200	[thread overview]
Message-ID: <20190813093707.GD15556@localhost> (raw)
In-Reply-To: <4e9b3ecf-ca45-51a5-d582-d3d067ecc723@gmx.net>

On Wed, Jul 31, 2019 at 07:32:29PM +0200, Markus Breunig wrote:
> 
> 
> Am 16.07.2019 um 11:23 schrieb Johan Hovold:
> > [ Pleas avoid top posting. ]
> >
> > On Sun, Jul 07, 2019 at 09:38:00PM +0200, Markus Breunig wrote:
> >> Hi Greg,
> >>
> >> also the company GNS has a fragmented homepage, the handbook ist
> >> available here:
> >> http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
> >> habe a look to page 10 "Remarks to Linux"
> >>
> >> This is the log of "lsusb -v" (full scan result attached):
> >>
> >> Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony
> >> 300/350 Remote
> >
> > Are you sure this is the right device? This looks like a remote control,
> > and one that should be using the cdc-acm driver.
> >
> 
> The output of lsusb before plugging the GNS5890 device into the USB-port:
> 
> Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
> Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
> SMSC9512/9514 Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> and the result of the lsusb after plugging the GNS5890 device into the
> USB-port:
> 
> Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
> Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard
> Bus 001 Device 006: ID 04d8:f8e8 Microchip Technology, Inc. Harmony
> 300/350 Remote
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
> SMSC9512/9514 Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Ok, thanks for confirming. 

Based on the below descriptors, this device should be handled by the
cdc-acm driver and show up as a /dev/ttyACMn.

Do you have that driver enabled? Can you enable debugging in that driver
and post the syslog from when plugging the device in if it still doesn't
work?

You can enable debugging using

	modprobe cdc-acm dyndbg==p

or through sysfs, see

	Documentation/admin-guide/dynamic-debug-howto.rst

> >> Device Descriptor:
> >>     bLength                18
> >>     bDescriptorType         1
> >>     bcdUSB               2.00
> >>     bDeviceClass          255 Vendor Specific Class
> >>     bDeviceSubClass         0
> >>     bDeviceProtocol         0
> >>     bMaxPacketSize0         8
> >>     idVendor           0x04d8 Microchip Technology, Inc.
> >>     idProduct          0xf8e8 Harmony 300/350 Remote
> >>     bcdDevice           48.12
> >>     iManufacturer           1
> >>     iProduct                2
> >>     iSerial                 3
> >>     bNumConfigurations      1
> >>     Configuration Descriptor:
> >>       bLength                 9
> >>       bDescriptorType         2
> >>       wTotalLength           67
> >>       bNumInterfaces          2
> >>       bConfigurationValue     1
> >>       iConfiguration          0
> >>       bmAttributes         0xc0
> >>         Self Powered
> >>       MaxPower              100mA
> >>       Interface Descriptor:
> >>         bLength                 9
> >>         bDescriptorType         4
> >>         bInterfaceNumber        0
> >>         bAlternateSetting       0
> >>         bNumEndpoints           1
> >>         bInterfaceClass         2 Communications
> >>         bInterfaceSubClass      2 Abstract (modem)
> >>         bInterfaceProtocol      1 AT-commands (v.25ter)
> >>         iInterface              0
> >>         CDC Header:
> >>           bcdCDC               1.10
> >>         CDC ACM:
> >>           bmCapabilities       0x02
> >>             line coding and serial state
> >>         CDC Union:
> >>           bMasterInterface        0
> >>           bSlaveInterface         1
> >>         CDC Call Management:
> >>           bmCapabilities       0x00
> >>           bDataInterface          1
> >>         Endpoint Descriptor:
> >>           bLength                 7
> >>           bDescriptorType         5
> >>           bEndpointAddress     0x82  EP 2 IN
> >>           bmAttributes            3
> >>             Transfer Type            Interrupt
> >>             Synch Type               None
> >>             Usage Type               Data
> >>           wMaxPacketSize     0x0008  1x 8 bytes
> >>           bInterval               2
> >>       Interface Descriptor:

Johan

      reply	other threads:[~2019-08-13  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5D1D1376.7070202@gmx.net>
2019-07-04 20:47 ` Fwd: Re: New USB Device Markus Breunig
2019-07-05  5:21   ` Greg KH
2019-07-07 19:38     ` Markus Breunig
2019-07-16  9:23       ` Johan Hovold
2019-07-31 17:32         ` Markus Breunig
2019-08-13  9:37           ` Johan Hovold [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190813093707.GD15556@localhost \
    --to=johan@kernel.org \
    --cc=Markus.L.Breunig@gmx.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).