All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: alsa-devel@alsa-project.org
Subject: force snd-usb-audio to use "Vendor Specific Class"
Date: Wed, 23 Jun 2010 15:29:25 +0200	[thread overview]
Message-ID: <1277299765.22499.42.camel@zwerg> (raw)

Hallo all,
is there any way to force snd-usb-audio to use some "Vendor Specific
Class" device?
i currently got two webcams from my friends to take a look on. They are
cheep gspca based webcams with Mic. I wont to test if snd-usb-audio can
use it if i force it. Devices it self do not provide any hints for the
driver.

lsusb -vd 093a:2468 | grep -i class
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass

regards,
Alexey

             reply	other threads:[~2010-06-23 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 13:29 Alexey Fisher [this message]
2010-06-23 13:36 ` force snd-usb-audio to use "Vendor Specific Class" Daniel Mack
2010-06-23 13:42   ` Daniel Mack
2010-06-24 10:36 ` Hans de Goede
2010-06-24 11:03   ` Alexey Fisher

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=1277299765.22499.42.camel@zwerg \
    --to=bug-track@fisher-privat.net \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.