Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Barknecht <fbar@footils.org>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creamware Noah, snd-usb-audio capable?
Date: Tue, 10 Feb 2004 22:36:17 +0100	[thread overview]
Message-ID: <20040210213617.GH10941@fliwatut.scifi> (raw)
In-Reply-To: <1076438161.2839.0.camel@chief.local>

Hallo,
Hartmut Geissbauer hat gesagt: // Hartmut Geissbauer wrote:

> reading the different entries in usbquirks.h it looks like they are
> taken from the usb-infos like lsusb provides. Is it very difficult to
> take the infos from lsusb and translate it to an quirk?
> I only need some quick advice and will try it by myself. A good
> (complex) example in my opinion is the "Roland SC-D70".

Well, others like Takashi or Clemens will be able to give better
answers,but I guess, it helps to get familiar with the USB-audio
specification. For example, for a short time I was investigating why
the Midi jacks on the Terratec Phase 26 aren't supported. 

I looked up the specification of usb-midi in
http://www.usb.org/developers/devclass_docs/midi10.pdf and also looked
very closely and for a long time at the lsusb output.  This interface
descriptor then looks very much like it must be the midi interface: 

    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      3 
      bInterfaceProtocol      0 
      iInterface              3 TerraTec PHASE 26 USB
  unknown descriptor type: 07 24 01 00 01 41 00
  unknown descriptor type: 06 24 02 01 10 00
  unknown descriptor type: 06 24 02 02 11 00
  unknown descriptor type: 09 24 03 01 12 01 11 01 00
  unknown descriptor type: 09 24 03 02 13 01 10 01 00
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
        bRefresh                0
        bSynchAddress           0
  unknown descriptor type: 05 25 01 01 10
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
        bRefresh                0
        bSynchAddress           0
  unknown descriptor type: 05 25 01 01 12
  Language IDs: (length=4)
     0409 English(US)


The main reason for my assumption is the value for bInterfaceNumber
which is "3" or 0x03 as it should be according to the USB spec which
requires for a "MIDI Adapter Standard MIDIStreaming Interface
Descriptor" to have this field set as follows: 

Offset Field                Size  Value   Description
...
6      bInterfaceSubclass   1     0x03   MIDISTREAMING.
...

All other bInterfaceNumber's in the Phase 26 output are *not* 3. (See
my entry on qbik.ch).

Unfortunatly that's as far as I got. I figure, now a quirk is needed,
but I don't know which one (it probably has something to do with the
endpoints or so.)

Nevertheless I don't have the Phase 26 anymore, so I cannot dig much
deeper.

ciao
-- 
 Frank Barknecht                               _ ______footils.org__


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-02-10 21:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 19:06 Creamware Noah, snd-usb-audio capable? Hartmut Geissbauer
2004-02-07  2:20 ` Paul Davis
2004-02-10 16:56   ` Frank Barknecht
2004-02-10 18:36     ` Hartmut Geissbauer
2004-02-10 21:36       ` Frank Barknecht [this message]
2004-02-10 22:08         ` Hartmut Geissbauer
2004-02-12 11:02           ` Clemens Ladisch
2004-02-14 20:14             ` Hartmut Geissbauer
2004-02-16 10:12               ` Clemens Ladisch
2004-02-16 18:18                 ` Hartmut Geissbauer
2004-02-16 18:36                 ` Hartmut Geissbauer
2004-02-17 12:43                   ` Clemens Ladisch
2004-02-17 17:04                     ` Hartmut Geissbauer
2004-02-18  8:03                       ` Clemens Ladisch
2004-02-18 18:59                         ` [partialy fixed] " Hartmut Geissbauer
2004-02-19  8:21                           ` Clemens Ladisch
2004-02-19 22:04                             ` Hartmut Geissbauer
2004-02-20 11:10                               ` Clemens Ladisch
2004-02-23 17:46                                 ` Hartmut Geissbauer
2004-02-26 10:39                                   ` Clemens Ladisch
2004-02-26 18:15                                     ` [fixed] " Hartmut Geissbauer
2004-02-24 19:07                                 ` [partialy fixed] " Hartmut Geissbauer
2004-02-11  9:46         ` Clemens Ladisch
2004-02-11 18:00           ` Frank Barknecht
2004-02-12 10:03             ` Clemens Ladisch
2004-02-12 17:52               ` Frank Barknecht

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=20040210213617.GH10941@fliwatut.scifi \
    --to=fbar@footils.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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