aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86/include/asm/swab.h
diff options
context:
space:
mode:
authorStefan Richter <stefanr@s5r6.in-berlin.de>2011-01-15 18:19:48 +0100
committerStefan Richter <stefanr@s5r6.in-berlin.de>2011-01-21 00:27:46 +0100
commit6044565af458e7fa6e748bff437ecc49dea88d79 (patch)
tree874808ca8f1d8f5413c8e9302e5f52d9c4cfb4f1 /arch/x86/include/asm/swab.h
parent1427130425c1239d977e8891c3a8923f53a6e352 (diff)
downloadkernel_samsung_smdk4412-6044565af458e7fa6e748bff437ecc49dea88d79.zip
kernel_samsung_smdk4412-6044565af458e7fa6e748bff437ecc49dea88d79.tar.gz
kernel_samsung_smdk4412-6044565af458e7fa6e748bff437ecc49dea88d79.tar.bz2
firewire: core: fix unstable I/O with Canon camcorder
Regression since commit 10389536742c, "firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder": The camcorder Canon MV5i generates lots of bus resets when asynchronous requests are sent to it (e.g. Config ROM read requests or FCP Command write requests) if the camcorder is not root node. This causes drop- outs in videos or makes the camcorder entirely inaccessible. https://bugzilla.redhat.com/show_bug.cgi?id=633260 Fix this by allowing any Canon device, even if it is a pre-1394a IRM like MV5i are, to remain root node (if it is at least Cycle Master capable). With the FireWire controller cards that I tested, MV5i always becomes root node when plugged in and left to its own devices. Reported-by: Ralf Lange Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Cc: <stable@kernel.org> # 2.6.32.y and newer
Diffstat (limited to 'arch/x86/include/asm/swab.h')
0 files changed, 0 insertions, 0 deletions