Hi all, Now that there's a kernel that supports it for Fedora 17 (kernel 3.6.1 needed for is_local), I've been trying out the kernel target's 1394 target support against Windows 7. - Windows device manager lists the device as "Linux Firewire UNKNOWN MODEL IEEE 1394 SBP2 device", I'm not sure if that's what we want or something more descriptive, or where it's getting this from, but that's what it's showing right now. - Behavior is strange when more than one LUN is exported. Drives may show up as cdrom when they're not, or as unwritable "RAW" partitions, or not all exported luns may appear. All further testing was with one lun. - Tried ramdisk, fileio, and tried the pscsi backstore with a cdrom, no issues. - Reading and writing performance seemed not-so-hot, and the file copy progress bar would stall for long periods, and then jump forward. - Windows didn't see the lun after I enabled the tpg on the target until after a reboot. (I didn't do any cable plugging/unplugging.) I seem to recall it showing up immediately when I tested this a few months ago, but maybe not. - When rebooting for the previous issue, Windows boot would get stuck at the logo screen - resetting a second time would let it boot all the way and see the exported lun. Maybe Windows is trying to optimize reboot or something and then having issues with the new device? Anyways, not like we can be responsible for Windows 1394 issues, but wanted to report this stuff in case there's stuff we need to fix on our side, or just document so users don't get tripped up. Thanks -- Regards -- Andy -- 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
