Changes between Version 6 and Version 7 of Specs/I²C/Protocol


Ignore:
Timestamp:
09/09/13 02:14:52 (11 years ago)
Author:
ph3-der-loewe
Comment:

+dev caps

Legend:

Unmodified
Added
Removed
Modified

  • Specs/I²C/Protocol

    v6 v7  
    8686Those parameters' meaning is depending on Device's Vendor ID, type and sub-type as well as parent device vendor ID, type and sub-type ID. 
    8787 
     88The GENERIC device defines that all the bits are used by the child device or set to zero. 
     89The BRIDGE device has the following Device Capabilities: 
     90||= Bit =||= Symbolic name =||= Description =|| 
     91||0      ||NETWORK          ||Network of any kind is present || 
     92||1      ||ETHERNET         ||Ethernet is present || 
     93||2      ||I2C              ||I²C interface is present || 
     94||3      ||SPI              ||SPI port is present || 
     95||4      ||DMX512           ||DMX512 port is present || 
     96||5      ||MIDI             ||MIDI port is present || 
     97||6      ||WAVEFORM         ||Waveform (Analog IO for equivalent spaces samples) port is present || 
     98||7      ||RESERVED7        ||Reserved for future use. || 
     99||8-23   ||                 ||Defined by subtype. || 
     100 
    88101=== Device Serial === 
    89102The serial of the device is given as a 16 byte bitstring. This is intended to be used to store an UUID as device serial. If a vendor uses some other numbering a schema neets to be established that maps those serials to the device serial field. A mapping should be chosen that complies with the current UUID standard.