alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Didier 'Ptitjes' Villevalois <ptitjes@free.fr>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: usb-audio: Reloop Play support (TI TUSB3200AC)
Date: Sat, 20 Oct 2012 14:49:50 +0200	[thread overview]
Message-ID: <50829DEE.7020004@gmail.com> (raw)
In-Reply-To: <1350728568.5932.6.camel@didier-laptop>

On 20.10.2012 12:22, Didier 'Ptitjes' Villevalois wrote:
> On ven., 2012-10-19 at 20:02 +0200, Daniel Mack wrote:
> [...]
>> Let me know of you make any progress here.
>>
> I diff-ed the ioreg output when the play is connected without the driver
> (-) and with the driver (+). So I can see that it is using its
> proprietary driver.
> 
> http://ptitjes.free.fr/reloop-play/play-ioreg-without-and-with-driver.diff

Hmm, that output doesn't make a whole lot of sense. Could you do the
same thing with lsusb under Linux? Boot into Linux after the OS X driver
downloaded the firmware for one run, and freshly connect (power cycle)
device for the other.

> I also traced (with Apple's USB Probe tool) the USB when connecting the
> PLAY.
> 
> At log level 6:
> http://ptitjes.free.fr/reloop-play/usb-log-withdriver-l6.txt
> 
> At log level 7: (3.5Mo!!)
> http://ptitjes.free.fr/reloop-play/usb-log-withdriver-l7.txt
> 
> I have to do the same thing when streaming some sound. But should I
> output some easily recognizable sound ? Something like a sine or some
> silence ?

Yes, that can help. You could for example stream a sine that is on just
one channel, so you can debug the muxing (interleaving) on the wire. Or
a sine at ~ -48dB, which would just leave the 8 MSB empty (to check the
endianess).

Most probably though, the streaming mode is already supported by the
Linux driver, and it's the recognition of the right format that fails,
or the cards needs a different setup sequence than the generic one.


Daniel

  reply	other threads:[~2012-10-20 12:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 13:09 usb-audio: Reloop Play support (TI TUSB3200AC) Didier 'Ptitjes' Villevalois
2012-10-19 13:20 ` Daniel Mack
     [not found]   ` <1350654327.8310.4.camel@didier-laptop>
2012-10-19 13:53     ` Daniel Mack
2012-10-19 15:09       ` Didier 'Ptitjes' Villevalois
2012-10-19 18:02         ` Daniel Mack
2012-10-20 10:22           ` Didier 'Ptitjes' Villevalois
2012-10-20 12:49             ` Daniel Mack [this message]
2012-10-20 13:03               ` Didier 'Ptitjes' Villevalois
2012-10-20 13:06                 ` Daniel Mack
2012-10-20 13:11                   ` Didier 'Ptitjes' Villevalois
2013-08-23 15:58                     ` Ansgar Scheffold
2012-10-19 15:28       ` Didier 'Ptitjes' Villevalois
2012-10-19 18:06         ` Daniel Mack
2012-10-20 14:30 ` Didier 'Ptitjes' Villevalois
2012-10-20 16:15   ` Clemens Ladisch
2012-10-21 13:38     ` Didier 'Ptitjes' Villevalois
2012-10-21 14:11       ` Clemens Ladisch
     [not found] ` <1350743061.25322.15.camel@didier-laptop>
2012-10-20 15:00   ` Daniel Mack

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=50829DEE.7020004@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ptitjes@free.fr \
    /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;
as well as URLs for NNTP newsgroup(s).