diff options
author | Stefan Richter <stefanr@s5r6.in-berlin.de> | 2008-12-13 22:12:06 (GMT) |
---|---|---|
committer | Stefan Richter <stefanr@s5r6.in-berlin.de> | 2009-01-04 22:50:34 (GMT) |
commit | 0bed1819687b50a769a1fee6d91cb0ef79b011b4 (patch) | |
tree | bc5c36dda1f8e8de697ca3bb2b4d170cb77183c6 /drivers/ieee1394/pcilynx.h | |
parent | c1fc58d63d754b82070881c62601551464afa19d (diff) | |
download | linux-fsl-qoriq-0bed1819687b50a769a1fee6d91cb0ef79b011b4.tar.xz |
ieee1394: ignore nonzero Bus_Info_Block.max_rom, fetch config ROM in quadlets
It is already known that buggy firmwares exist which report a bogus
link_spd in their config ROM bus info block. We now got the first
report of a bogus max_rom too (Freecom FireWire Hard Drive 1TB,
http://bugzilla.kernel.org/show_bug.cgi?id=12206).
I suspect other OSs only use quadlet reads to fetch the config ROM,
otherwise the firmware authors would have noticed their mistake.
Hence limit ieee1394's config ROM fetching routine to quadlets as the
safe minimum regardless of what the bus info block says.
This will potentially slow the bus reset handling by nodemgr somewhat
down. But most existing devices support only quadlet reads anyway,
hence there will often be no actual difference to before this change.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'drivers/ieee1394/pcilynx.h')
0 files changed, 0 insertions, 0 deletions