Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hartmut Geissbauer <nwgbh@swissonline.ch>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creamware Noah, snd-usb-audio capable?
Date: Tue, 10 Feb 2004 19:36:02 +0100	[thread overview]
Message-ID: <1076438161.2839.0.camel@chief.local> (raw)
In-Reply-To: <20040210165602.GC9524@fliwatut.scifi>

Hello,
Frank Barknecht wrote:
> Hallo, 
> Paul Davis hat gesagt: // Paul Davis wrote:
> 
> > >    Interface Descriptor:
> > >      bLength                 9
> > >      bDescriptorType         4
> > >      bInterfaceNumber        0
> > >      bAlternateSetting       0
> > >      bNumEndpoints           6
> > >      bInterfaceClass       255 Vendor Specific Class
> > 				 ^^^^^^^^^^^^^^^^^^^^^
> > 
> > i don't know much about USB at, but this doesn't look good.
> 
> But it doesn't necessarily have to be that bad as well. Several of the
> (now) supported USB devices have "Vendor Specific" classes, for
> example most Edirol devices do. But I guess, that yes: you'll probably
> need quirks then in usbquirks.h for the Noah, too. 
> 
> ciao

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

Thanks in advance for any help.

Hartmut  

-- 

Hartmut Geissbauer <nwgbh@swissonline.ch>



-------------------------------------------------------
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 18: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 [this message]
2004-02-10 21:36       ` Frank Barknecht
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=1076438161.2839.0.camel@chief.local \
    --to=nwgbh@swissonline.ch \
    --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