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: Greg KH <gregkh@linuxfoundation.org>, linux-usb@vger.kernel.org
Subject: Re: Fwd: Re: New USB Device
Date: Tue, 16 Jul 2019 11:23:05 +0200	[thread overview]
Message-ID: <20190716092305.GC3522@localhost> (raw)
In-Reply-To: <5D224A18.2070907@gmx.net>

[ 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.

> 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:
>        bLength                 9
>        bDescriptorType         4
>        bInterfaceNumber        1
>        bAlternateSetting       0
>        bNumEndpoints           2
>        bInterfaceClass        10 CDC Data
>        bInterfaceSubClass      0 Unused
>        bInterfaceProtocol      0
>        iInterface              0
>        Endpoint Descriptor:
>          bLength                 7
>          bDescriptorType         5
>          bEndpointAddress     0x03  EP 3 OUT
>          bmAttributes            2
>            Transfer Type            Bulk
>            Synch Type               None
>            Usage Type               Data
>          wMaxPacketSize     0x0040  1x 64 bytes
>          bInterval               0
>        Endpoint Descriptor:
>          bLength                 7
>          bDescriptorType         5
>          bEndpointAddress     0x83  EP 3 IN
>          bmAttributes            2
>            Transfer Type            Bulk
>            Synch Type               None
>            Usage Type               Data
>          wMaxPacketSize     0x0040  1x 64 bytes
>          bInterval               0

> Am 05.07.2019 07:21, schrieb Greg KH:
> > On Thu, Jul 04, 2019 at 10:47:47PM +0200, Markus Breunig wrote:
> >> Hi Greg,
> >>
> >> using a serial device driver is the idea of the manufacturer
> >> "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some
> >> hints to use the device are given via usbserial.
> >
> > Any pointers to those instructions?
> >
> >> In practice the "GNS 5890 ADS-B Receiver" is similare to some GPS
> >> Receivers with NMEA 0183 interface starting to send information on the
> >> serial interface after power on and signal availabillity (with 115200
> >> boud data rate).

Johan

  reply	other threads:[~2019-07-16  9:23 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 [this message]
2019-07-31 17:32         ` Markus Breunig
2019-08-13  9:37           ` Johan Hovold

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=20190716092305.GC3522@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).