From: Clemens Ladisch <clemens@ladisch.de>
To: sboyce@blueyonder.co.uk, Daniel Mack <daniel@caiaq.de>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@alsa-project.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.35-rc3 E-MU 0404 USB problem
Date: Wed, 23 Jun 2010 14:45:19 +0200 [thread overview]
Message-ID: <4C2201DF.9050500@ladisch.de> (raw)
In-Reply-To: <4C21E875.20200@blueyonder.co.uk>
>>> Sid Boyce wrote:
>>>> Transmit fails,
What exactly fails?
>>>> dmesg output with 48K sample rate set is:-
>>>> ALSA sound/usb/clock.c:214: 6:2:3: endpoint lacks sample rate attribute bit, cannot set.
There are many devices that have only one sample rate or that have one
sample rate per alternate setting. This doesn't deserve a message, much
less a warning.
Regards,
Clemens
WARNING: multiple messages have this Message-ID (diff)
From: Clemens Ladisch <clemens@ladisch.de>
To: sboyce@blueyonder.co.uk, Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org, alsa-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: 2.6.35-rc3 E-MU 0404 USB problem
Date: Wed, 23 Jun 2010 14:45:19 +0200 [thread overview]
Message-ID: <4C2201DF.9050500@ladisch.de> (raw)
In-Reply-To: <4C21E875.20200@blueyonder.co.uk>
>>> Sid Boyce wrote:
>>>> Transmit fails,
What exactly fails?
>>>> dmesg output with 48K sample rate set is:-
>>>> ALSA sound/usb/clock.c:214: 6:2:3: endpoint lacks sample rate attribute bit, cannot set.
There are many devices that have only one sample rate or that have one
sample rate per alternate setting. This doesn't deserve a message, much
less a warning.
Regards,
Clemens
next prev parent reply other threads:[~2010-06-23 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 12:58 2.6.35-rc3 E-MU 0404 USB problem Sid Boyce
2010-06-22 13:11 ` Greg KH
2010-06-22 13:34 ` Daniel Mack
2010-06-23 10:56 ` Sid Boyce
2010-06-23 12:45 ` Clemens Ladisch [this message]
2010-06-23 12:45 ` Clemens Ladisch
2010-06-24 2:17 ` Sid Boyce
2010-06-23 17:49 ` James Courtier-Dutton
2010-06-24 2:29 ` Sid Boyce
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=4C2201DF.9050500@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=daniel@caiaq.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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.