From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Peter Oehry <peter.oehry@gmx.li>,
Thibault Le Meur <Thibault.LeMeur@supelec.fr>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: snd-usb-audio - Driver for M-Audio Fast Track Pro
Date: Mon, 14 Aug 2006 13:16:36 +0200 [thread overview]
Message-ID: <1155554196.1617.268317929@webmail.messagingengine.com> (raw)
In-Reply-To: <20060813214825.5654969E159@zeus.olymp.home>
Peter Oehry wrote:
> Thibault Le Meur <Thibault.LeMeur@supelec.fr> wrote:
> 2. Another interesting thing is that in fact the device sensds the data
> little endian in 16-Bit mode and big endian in 24-Bit mode.
IIRC other M-Audio devices to that, too. The reasons seems to be that
the device is basically big-endian, but the 16-bit interfaces are
designed to work with Windows' usbaudio.sys.
> For what I think it should be possible to switch modes without restarting
> the kernel module and switch on and off the device. It should be possible
> to switch the mode by resetting all interfaces and setting up the new
> altsets like the windows driver does. This would eventually need a new
> proc interace
Why proc?
If the configuration needs to be changed at runtime, and if the driver
cannot do this automatically, a mixer control would be the best solution.
> How do I know if I also need a quirk for the midi devices?
You need a quirk when there aren't any class-specific descriptors for
the MIDI port.
Regards,
Clemens
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-08-14 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 16:16 snd-usb-audio - Driver for M-Audio Fast Track Pro peter.oehry
2006-08-08 17:02 ` Clemens Ladisch
2006-08-08 18:23 ` Thibault Le Meur
2006-08-09 3:19 ` Thierry Vignaud
2006-08-09 8:26 ` Thibault Le Meur
2006-08-08 18:47 ` Peter Oehry
2006-08-08 20:22 ` Thibault Le Meur
2006-08-08 21:41 ` Peter Oehry
2006-08-08 22:07 ` Thibault Le Meur
2006-08-10 21:33 ` Peter Oehry
2006-08-11 9:20 ` Thibault Le Meur
2006-08-13 21:48 ` Peter Oehry
2006-08-14 9:57 ` Thibault Le Meur
2006-08-14 11:16 ` Clemens Ladisch [this message]
2006-08-14 12:14 ` peter.oehry
2006-08-20 12:19 ` Peter Oehry
2006-08-28 14:31 ` Thierry Vignaud
2006-08-29 20:53 ` Peter Oehry
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=1155554196.1617.268317929@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=Thibault.LeMeur@supelec.fr \
--cc=alsa-devel@lists.sourceforge.net \
--cc=peter.oehry@gmx.li \
/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