On 2011-04-13 21:50 +0200, RafaÅ MiÅecki wrote: > Note for not involved: AMBA is family with few buses/interfaces > possible: AXI, AHB, ASB, APB, ATB [1]. > > So what are you saying is that drivers/amba/ is for AMBA APB? OK, I > can accept such a explanation and it makes me even more sure we need > another AMBA driver (this time: AMBA AXI). I believe the drivers/amba code is mainly (only?) for ARM PrimeCell cores which all include identification information at the end of their memory maps. There are PrimeCell cores available for most if not all AMBA bus interfaces. Non-primecell cores might not have such identification, and therefore would not be usable with drivers/amba. They are generally used with the platform bus. > The left question is: how much of the implemented code is AMBA AXI > specific and how much is Broadcom specific? > 1) Does AMBA AXI identify cores by manuf, id, rev and class? Is this > really AMBA AXI specific and a evolution from simple "id" in AMBA APB? > 2) Is this standard for AMBA AXI to keep list of available cores in > some specific memory (is this always EPROM like in case of Bcm?)? I don't believe AXI (the physical bus) nor any other AMBA bus interface provides any mechanism whatsoever for device identification or enumeration. -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
