Stefan Richter wrote:
do you know of a specific series of SBP-2 firmwares which do
actually support READ CAPACITY (16) properly but are treated by Linux as
if they wouldn't? If so, we could add a workaround to our drivers to
treat them like recent SBC implementations. We would have to match
against their firmware_revision field which you get logged in dmesg if
you load the sbp2 or firewire-sbp2 driver with the module parameter
workarounds=0x1000.
PS:
# modprobe -r sbp2
# modprobe sbp2 workarounds=0x1000
(plug the disk in, wait 5 or 10 seconds or so)
# dmesg
Use firewire-sbp2 instead of sbp2 if your distribution already uses the
newer firewire drivers which are alternatively available in recent
kernel versions. E.g. on Fedora.
--
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
