On 11/05/2014 04:45 PM, Matthias Klein wrote: > The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the > I2S interface.
BTW, according to: http://raspberryalphaomega.org.uk/2013/02/06/automatic-raspberry-pi-board-revision-detection-model-a-b1-and-b2/ ... there are actually 2 different HW configurations we care about for the pre-plus Pis: B rev 1 A, or B rev 2 I guess we should have separate device trees for those, since there are some differences in the GPIO and I2C channel usage. That'd leave us with: bcm2835-rpi-b.dts (Pin3=GPIO0, Pin5=GPIO1, Pin13=GPIO21, I2C-0) bcm2835-rpi-b-rev2.dts (Pin3=GPIO1, Pin5=GPIO2, Pin13=GPIO27, 12C-1) bcm2835-rpi-b-plus.dts (TBD pending schematic or equivalent info) ... and probably another for the compute board. We can ignore RAM size differences, since these are automatically filled into the /memory node in DT. I'm not sure if A-vs-B-rev-1 is interesting. Perhaps we should have separate DTs just in case, since we may need to represent the LAN_RUN GPIO in DT at some point, and that only applies to the B. Presumably, the boot loader would automatically query the VC firmware for the board revision data, and dynamically load the appropriate DT filename. Any thoughts or objections? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
