linux-kernel - Re: [RFC][PATCH] axi: add AXI bus driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110413204924.GA1063@elliptictech.com>
Date:	Wed, 13 Apr 2011 16:49:24 -0400
From:	Nick Bowler <nbowler@...iptictech.com>
To:	Rafał Miłecki <zajec5@...il.com>
Cc:	Arend van Spriel <arend@...adcom.com>,
	George Kashperko <george@...u.edu.ua>,
	"balbi@...com" <balbi@...com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>,
	"b43-dev@...ts.infradead.org" <b43-dev@...ts.infradead.org>,
	Michael Büsch <mb@...sch.de>,
	Larry Finger <Larry.Finger@...inger.net>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Russell King <rmk@....linux.org.uk>,
	Arnd Bergmann <arnd@...db.de>,
	Andy Botting <andy@...ybotting.com>,
	linuxdriverproject <devel@...uxdriverproject.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] axi: add AXI bus driver

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/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/