On Thu, Nov 01, 2012 at 05:32:25PM +0200, Pantelis Antoniou wrote: > Capebus is created to address the problem of many SoCs that can provide a > multitude of hardware interfaces but in order to keep costs down the main > boards only support a limited number of them. The rest are typically brought > out to pin connectors on to which other boards, named capes are connected and > allow those peripherals to be used. > > These capes connect to the SoC interfaces but might also contain various other > parts that may need some kind of driver to work. I've not yet actually looked at the code but this sounds very similar to some work I wanted to do on handling coldpluggable modules on reference designs. In that case it's not so much about pin count as about the fact that we have to detect at runtime what's connected to the system but I think the overall effect is very similar and there's definite overlap. Can you please CC me on future versions of the code? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
