linux-kernel - Re: [RFC-v2 0/7] Capebus; a bus for SoCs using simple expansion connectors

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: <20130114022326.GA4928@sirena.org.uk>
Date:	Mon, 14 Jan 2013 02:23:27 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Pantelis Antoniou <panto@...oniou-consulting.com>
Cc:	Tony Lindgren <tony@...mide.com>, Paul Walmsley <paul@...an.com>,
	"Hiremath, Vaibhav" <hvaibhav@...com>,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	Koen Kooi <koen@...inion.thruhere.net>,
	Matt Porter <mporter@...com>, Russ Dill <Russ.Dill@...com>,
	linux-omap@...r.kernel.org
Subject: Re: [RFC-v2 0/7] Capebus; a bus for SoCs using simple expansion
 connectors

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