From: Daniel Mack <daniel@caiaq.de>
To: Jan Depner <eviltwin69@cableone.net>
Cc: ALSA_DEVEL <alsa-devel@alsa-project.org>
Subject: Re: TASCAM US-1641
Date: Wed, 24 Mar 2010 23:50:20 +0100 [thread overview]
Message-ID: <20100324225020.GO30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <1269468166.7429.7.camel@eviltwin>
On Wed, Mar 24, 2010 at 05:02:46PM -0500, Jan Depner wrote:
> On Wed, 2010-03-24 at 06:56 +0100, Daniel Mack wrote:
> > On Tue, Mar 23, 2010 at 08:34:43PM -0500, Jan Depner wrote:
> > I suggest adding some printk()s to the driver and see what it actually
> > does and which values it passes around. Most probably there is more
> > differences in the data format, and descriptors and/or message blocks
> > have different meanings for this hardware model.
> >
>
> I did as suggested and got back reasonable appearing numbers for
> rate, use_packsize, and period_frames of 44100, 36, and 256 respectively
> but am not sure how to relate this to my interface. Is there some
> documentation somewhere that would explain the output of lsusb -v with
> respect to variable names in us122l.c. My problem here is that I don't
> know what would actually be reasonable for this interface nor how to
> find out.
Sorry I can't really help here. I've never dealt with any TASCAM
interface, and I don't know how close they are to any USB class
interface. Maybe Karsten can tell us more about that.
> Many thanks for your help with this. Karsten had asked me to get
> back with him if I got one of these but my email to him must have gone
> to the spam filter as I haven't heard anything.
Cc'ed him on this mail :)
Daniel
next prev parent reply other threads:[~2010-03-24 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 1:34 TASCAM US-1641 Jan Depner
2010-03-24 5:56 ` Daniel Mack
2010-03-24 22:02 ` Jan Depner
2010-03-24 22:50 ` Daniel Mack [this message]
2010-03-25 10:00 ` Karsten Wiese
2010-03-25 23:48 ` Jan Depner
2010-03-25 10:03 ` Karsten Wiese
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=20100324225020.GO30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=eviltwin69@cableone.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