fireworks: supplement for device entries

According to information given by Echo Audio, the actual ids for device which
use Fireworks board are clear.
firewire-lib/fireworks/bebob: code format for increment
fireworks: supplement hardware capabilities flag and remove needless members

According to information given by Echo Audio, all of flags for hardware
capabilities are clear. My understanding for flags of digital interfaces is
wrong.
fireworks: add new commands to change response address and to set transmit mode

According to information given by Echo Audio, Some commands are disclosed.
This commit add two of them.

1.change response address
Echo Fireworks Command(a.k.a EFC) uses a set of address. 0xecc000000000 is for
command and 0xecc080000000 is for response. The address for response can be
changed by command.

2.set transmit mode
Fireworks has two modes for transmit in a point of timestamp processing. One is
for Microsoft Windows and another is for IEC61883-1/6 compliant mode. In
Windows mode, all of 32bit field in second CIP header of AMDTP transmit packet
is used for 'presentation timestamp'. The value of this field is 0x90ffffff in
NODATA packet,
fireworks: supplement for label of hardware metering

According to information given by Echo Audio, Gibson RIP series have own labels
for hardware meter.
firewire-lib: add transfer delay tp timestamp from received packet to transmit packet

In IEC61883-6, the value of SYT field is 'presentation timestamp'. This value
means time expected for samples in the packet.

Additionally this value is used to synchronize transmitter and receiver. Then
the receiver reproduce timestamp for its tranmitting packets. In this case,
the transmitter is a master of synchronization.

This commit adds transfer delay to received timestamp for transmitting packet.
This is for the case that the device is a master of synchronization in AMDTP
blocking mode.

Logically this is better because in the device side, the received timestamp
(generated by transmitting packet) without transfer delay is the post.

But the width of this field is just 16bit. The value cannot describe whole of
timestamp. Then the cycle of the value is too fast. Then, standing a certan
range of time, the device cannot distinguish past timestamp from current
timestamp.

Actually the device works well without this commit.