[alsa-devel] Toneweal / Trigaudio FW66 device

[Daniel Jozsef]

Hello Takashi,

Thanks for getting involved, I really appreciate it! :D I was away this
week, but today I was able to run the commands you mentioned.

$ ./firewire-request /dev/fw1 fcp 0x01ff3000ffffffff
response: 000: 0c ff 30 07 0f 00 23 27                         ..0...#'
$ ./firewire-request /dev/fw1 fcp 0x01ff3100ffffffff
response: 000: 0c ff 31 00 08 60 ff ff                         ..1..`..
$ ./firewire-request /dev/fw1 fcp 0x01ff0200ffffffff
response: 000: 0c ff 02 00 02 02 04 03                         ........
$ ./firewire-request /dev/fw1 fcp 0x01080200ffffffff
response: 000: 0c 08 02 00 04 01 ff ff                         ........
$ ./firewire-request /dev/fw1 fcp 0x01600200ffffffff
response: 000: 0c 60 02 00 06 05 ff ff                         .`......

>From what I gather from the reference you linked, this seems more or less
what's expected, though I'm not entirely sure yet what it means for the
device to have 6 destination and 5 source plugs on the music subunit... :D
(If I read the specs correctly...)

Daniel


On Mon, Jan 20, 2020 at 2:19 PM Takashi Sakamoto <o-takashi at sakamocchi.jp>
wrote:

> 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 at 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
>