From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Daniel Jozsef <daniel.jozsef@gmail.com>
Cc: alsa-devel@alsa-project.org, ffado-user@lists.sourceforge.net
Subject: Re: [alsa-devel] Toneweal / Trigaudio FW66 device
Date: Mon, 20 Jan 2020 23:19:02 +0900 [thread overview]
Message-ID: <20200120141901.GA32472@workstation> (raw)
In-Reply-To: <CAK5Eu=sS8kMe5hCPgTx+V6AjzcCo3vN73tEQ1f=kY03Y2_CcJQ@mail.gmail.com>
Hi Daniel,
On Mon, Jan 20, 2020 at 11:42:34AM +0000, Daniel Jozsef wrote:
> Thanks for the quick reaction, Takashi :) I ran the command you mentioned,
> and your guess was spot on:
>
> daniel@gibbonmoon:~/opt/linux-firewire-utils-0.4/src$ ./firewire-request
> /dev/fw1 read 0xffffc8020000 60
> result: 000: 62 72 69 64 67 65 43 6f 03 00 00 00 00 00 00 00 bridgeCo........
> result: 010: 00 27 23 00 00 00 00 02 02 00 00 00 00 00 00 00 .'#.............
> result: 020: 32 30 31 30 30 35 32 35 31 32 31 35 30 34 20 20 20100525121504
> result: 030: 02 00 02 00 ff ff ff 00 80 00 0c 40 7c e3 13 00 ...........@|...
> result: 040: 32 30 30 38 31 32 30 32 31 33 34 34 34 38 20 20 20081202134448
> result: 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Yep, it's an application of BeBoB solution.
As a next step, please get responses against 5 AV/C commands below:
(AV/C UNIT INFO command)
$ ./firewire-request /dev/fw1 fcp 0x01ff3000ffffffff
response: 000: 0c ff 30 07 0f 00 14 96 ..0.....
(AV/C SUBUNIT INFO command)
$ ./firewire-request /dev/fw1 fcp 0x01ff3100ffffffff
response: 000: 0c ff 31 00 08 60 ff ff ..1..`..
(AV/C PLUG INFO command for Unit)
$ ./firewire-request /dev/fw1 fcp 0x01ff0200ffffffff
response: 000: 0c ff 02 00 02 02 01 01 ........
(AV/C PLUG INFO command for Audio subunit)
$ ./firewire-request /dev/fw1 fcp 0x01080200ffffffff
response: 000: 0c 08 02 00 02 02 ff ff ........
(AV/C PLUG INFO command for Music subunit)
$ ./firewire-request /dev/fw1 fcp 0x01600200ffffffff
response: 000: 0c 60 02 00 03 03 ff ff .`......
If you're interested in their contents, please refer to document published by
1394 Trading Association:
AV/C Digital Interface Command Set General Specification Version 4.2
(1394 Trading Association, September 1, 2004)
http://1394ta.org/wp-content/uploads/2015/07/2004006.pdf
Thanks
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-01-20 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK5Eu=tVQjBn+YvsHOLqSEir5aV8Q0hA1OgFiJZYdqnspdMz-Q@mail.gmail.com>
[not found] ` <CAK5Eu=snx3s9r9hoeF4Th0V0YXJYa=7PKUqDn3W4NdWZben-zg@mail.gmail.com>
[not found] ` <CAK5Eu=v2x+zFhCygKq8DPWd+CH5JTpZEayg=k2NvaTY7DUNA9g@mail.gmail.com>
[not found] ` <CAK5Eu=ucuW6Pp=+j7afPoYgPUdFXjh+PZ-PK6mc+m61M80ZndA@mail.gmail.com>
2020-01-19 16:43 ` [alsa-devel] [FFADO-user] Toneweal / Trigaudio FW66 device Takashi Sakamoto
2020-01-20 11:42 ` Daniel Jozsef
2020-01-20 14:19 ` Takashi Sakamoto [this message]
2020-01-24 22:16 ` [alsa-devel] " Daniel Jozsef
2020-01-25 3:18 ` Takashi Sakamoto
2020-01-28 22:28 ` Daniel Jozsef
2020-01-29 3:16 ` Takashi Sakamoto
2020-02-04 16:40 ` Daniel Jozsef
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=20200120141901.GA32472@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.jozsef@gmail.com \
--cc=ffado-user@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).