linux-kernel - Re: [PATCH] drivers: brcmaxi: provide amba axi functionality in separate module

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: <BANLkTinUWNvkigqkOQeYsyaAKnVXOCji8w@mail.gmail.com>
Date:	Sat, 23 Apr 2011 14:33:21 +0200
From:	Jonas Gorski <jonas.gorski@...il.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	"zajec5@...il.com" <zajec5@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"b43-dev@...ts.infradead.org" <b43-dev@...ts.infradead.org>,
	George Kashperko <george@...u.edu.ua>,
	Hauke Mehrtens <hauke@...ke-m.de>,
	Russell King <rmk@....linux.org.uk>,
	Larry Finger <Larry.Finger@...inger.net>,
	Andy Botting <andy@...ybotting.com>, Greg KH <greg@...ah.com>,
	Michael Buesch <m@...s.ch>
Subject: Re: [PATCH] drivers: brcmaxi: provide amba axi functionality in
 separate module

On 21 April 2011 16:38, Arend van Spriel <arend@...adcom.com> wrote:
> Would it be possible to make chipcommon driver optional (not doing the
> initialization)?

This would need to be done on a per-device/bus basis, at least for
embedded. Consider the following setup (which is quite common for dual
band routers):

BCM4718
+- Common Core <- provides flash write access, GPIOs, watchdog, ...
+- 802.11 Core <- for 2.4Ghz wifi
+- PCIe Core
  + BCM43224
    +- Common Core
    +- 802.11 Core <- for 5Ghz wifi

(I omitted any cores not relevant for the example)

So eventually you want to able to drive both 802.11 cores, but can't
exclusively claim both common cores.

Regards
Jonas
--
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/