linux-kernel - Re: [RFC-v2 1/7] capebus: Core capebus support

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] [day] [month] [year] [list]

Message-ID: <20130114023439.GB4928@sirena.org.uk>
Date:	Mon, 14 Jan 2013 02:34:39 +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 1/7] capebus: Core capebus support

On Thu, Nov 01, 2012 at 05:32:26PM +0200, Pantelis Antoniou wrote:
> Introducing capebus; a bus that allows small boards (capes) to connect
> to a complex SoC using simple expansion connectors.
> 
> Up to now to support these kind of boards, one had to hack the board files,
> and do all sort of gymnastics to handle all the different cases of
> conflict resolution.

Would it be possible to split out the DT support from the underlying
bus?  Looking at the code it seems like we're relying on DT for a lot of
the functionality when it comes to mapping devices into the system but
that doesn't really meet what I'm looking for.  One of the use cases I
have is supporting modules which can be used with multiple systems so I
really want to be able to just define the modules once and then have a
layer in the subsystem which remaps the connections onto the actual
hardware.
--
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/