2011/4/8 RafaÅ MiÅecki <zajec5@xxxxxxxxx>: > 2011/4/6 Arend van Spriel <arend@xxxxxxxxxxxx>: >> 3. Device identification >> >> The cores are identified by manufacturer, core id and revision in your >> patch. I would not use the revision because 4 out of 5 times a revision >> change does indicate a hardware change but no change in programming >> interface. The enumeration data does contain a more selective field >> indicating the core class (4 bits following the core identifier). I suggest >> to replace the revision field by this class field. > > Could you say something more about *class*, please? For my BCM43224 it > seems to be 0x0. WIll check BCM4313 in a moment. Same for BCM4313. BCM43224: axi: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x22, class 0x0) axi: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x17, class 0x0) axi: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x0F, class 0x0) BCM4313 axi: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x24, class 0x0) axi: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x18, class 0x0) axi: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x11, class 0x0) -- RafaÅ _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
