summaryrefslogtreecommitdiffstats
path: root/drivers/isdn/isdnloop
diff options
context:
space:
mode:
authorChris Boot <bootc@bootc.net>2012-02-15 15:59:08 +0100
committerStefan Richter <stefanr@s5r6.in-berlin.de>2012-02-22 22:36:01 +0100
commit8ff6a75744dfc0ea19a03c0ac5a438ef8d825342 (patch)
tree218244aab1394d4823df06ccdab08248dc756aa3 /drivers/isdn/isdnloop
parentfirewire: nosy: Use the macro DMA_BIT_MASK(). (diff)
downloadlinux-8ff6a75744dfc0ea19a03c0ac5a438ef8d825342.tar.xz
linux-8ff6a75744dfc0ea19a03c0ac5a438ef8d825342.zip
firewire: sbp2: Take into account Unit_Unique_ID
If the target's unit directory contains a Unit_Unique_ID entry, we should use that as the target's GUID for identification purposes. The SBP-2 standards document says: "Although the node unique ID (EUI-64) present in the bus information block is sufficient to uniquely identify nodes attached to Serial Bus, it is insufficient to identify a target when a vendor implements a device with multiple Serial Bus node connections. In this case initiator software requires information by which a particular target may be uniquely identified, regardless of the Serial Bus access path used." [ IEEE T10 P1155D Revision 4, Section 7.6 (page 51) ] and [ IEEE T10 P1467D Revision 5, Section 7.9 (page 74) ] Signed-off-by: Chris Boot <bootc@bootc.net> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'drivers/isdn/isdnloop')
0 files changed, 0 insertions, 0 deletions