> It's not really an instruction-set architecture issue, it's a binding > issue. What if a non-OF embedded SPARC comes along that copies i2c from > a PowerPC DTS file, or we come across a real-OF PowerPC that does it the > SPARC way? Like PowerMac ? :-) Apple additionally have different ways of representing multiple busses on one controller though. On some machines, they just use bits 0xF00 of the address as the bus number, which is a bit gross, and on some, they have sub-nodes i2c-bus@NN under the controller. But at least the address encoding (shifted by 1 bit) is common with sparc and I think is a fairly common way of representing i2c addresses. > As far as I can tell from poking around > http://penguinppc.org/historical/dev-trees-html/, they don't include reg > at all for i2c clients. Most of the device-trees on penguinppc.org are obsolete. i2c is mostly used in the device-tree for newer stuff such as G5s. Ben. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
