Hi folks, Well after lots of work I have a working and generally (at least I think) sensible starting point for the FireWire target. It appears to work fine in all the configurations I've tested it against, including Linux and Mac OS X initiators. This is not production ready code, and not ready for merging IMO. I know my locking (or more the lack of it) leaves something to be desired, and I know my use of atomics and memory barriers is wrong too. Performance is also a bit meagre and I'm sure it can be improved substantially - I already have some ideas for things that can be improved. For testing, I use: GUID=5254000b8f01e6f6 DIR_ID=abcdef modprobe firewire-sbp-target mkdir /sys/kernel/config/target/sbp mkdir /sys/kernel/config/target/sbp/$GUID mkdir /sys/kernel/config/target/sbp/$GUID/tpgt_1 mkdir /sys/kernel/config/target/sbp/$GUID/tpgt_1/lun/lun_0 ln -s /sys/kernel/config/target/core/iblock_0/sbptest /sys/kernel/config/target/sbp/$GUID/tpgt_1/lun/lun_0/sbptest echo $DIR_ID > /sys/kernel/config/target/sbp/$GUID/tpgt_1/directory_id echo 1 > /sys/kernel/config/target/sbp/$GUID/tpgt_1/enable Setting the directory_id is optional and something I have only just added, but it appears to work as planned. Any and all comments much appreciated. Thanks, Chris -- Chris Boot bootc@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
