summaryrefslogtreecommitdiff
path: root/firmware/emi62
diff options
context:
space:
mode:
authorTakashi Sakamoto <o-takashi@sakamocchi.jp>2015-10-11 13:33:50 (GMT)
committerTakashi Iwai <tiwai@suse.de>2015-10-11 16:14:01 (GMT)
commit2a7e1713cd652e7d2fdb54057fb6b2508cab15dc (patch)
treeb75197f077feaef197fda7aeacd7e26785473baa /firmware/emi62
parent6b9866c893fc6a51e74df65fd9d9f851a3c2872e (diff)
downloadlinux-2a7e1713cd652e7d2fdb54057fb6b2508cab15dc.tar.xz
ALSA: firewire-lib: continue packet processing at detecting wrong CIP headers
In firewire-lib, isochronous packet streaming is stopped when detecting wrong value for FMT field of CIP headers. Although this is appropriate to IEC 61883-1 and 6, some BeBoB based devices with vendors' customization use invalid value to FMT field of CIP headers in the beginning of streaming. $ journalctl snd-bebob fw1.0: Detect unexpected protocol: 01000000 8000ffff I got this log with M-Audio FireWire 1814. In this line, the value of FMT field is 0x00, while it should be 0x10 in usual AMDTP. Except for the beginning, these devices continue to transfer packets with valid value for FMT field, except for the beginning. Therefore, in this case, firewire-lib should continue to process packets. The former implementation of firewire-lib performs it. This commit loosens the handling of wrong value, to continue packet processing in the case. Fixes: 414ba022a528 ('ALSA: firewire-lib: add support arbitrary value for fmt/fdf fields in CIP header') Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'firmware/emi62')
0 files changed, 0 insertions, 0 deletions