On 10/02/2012 19:17, Andy Grover wrote:
On 02/09/2012 03:51 PM, Stefan Richter wrote:
On Feb 09 Chris Boot wrote:
1. Maps SAM target ports to IEEE-1212 units.
2. Insists that a target port within the target framework is named using
an EUI-64/GUID and exposes this in the IEEE-1212 unit directory's
Unit_Unique_ID property.
So now we need to support unit unique ID in our initiator too.
I haven't really been getting the whole discussion while you guys speak
1394-ese, but does this mean that other initiators (Mac, Win) won't work
with our target unless they also support Unit_Unique_ID??
Andy,
No, they'll work just fine. It's just that if you happen to have two
separate FireWire cards on the same bus an initiator that doesn't look
at the Unit_Unique_ID might see the same target twice, instead of one
instance of a single target. Even in this unlikely situation it
shouldn't be a problem, but the initiator may keep attempting to login
to the second instance of the target forever.
HTH,
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
