linux-kernel - Re: RFC: Platform data for onboard USB assets

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 24 Mar 2011 12:56:20 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Jaswinder Singh <jaswinder.singh@...aro.org>,
	andy.green@...aro.org, Andy Green <andy@...mcat.com>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>, arnd@...db.de,
	roger.quadros@...ia.com, greg@...ah.com, benh@...nel.crashing.org,
	Nicolas Pitre <nicolas.pitre@...aro.org>
Subject: Re: RFC: Platform data for onboard USB assets

On Tue, Mar 22, 2011 at 03:12:48PM +0000, Mark Brown wrote:
> On Tue, Mar 22, 2011 at 08:32:28PM +0530, Jaswinder Singh wrote:
> 
> > It's a different matter that DT has many hearts to win(at least in ARM
> > Linux)
> > So, perhaps the answer to Q(a) is - Yes.
> 
> It's not really a question of hearts to win.  Even for people who are
> fully won over the implementation just isn't there in mainline and it's
> not clear when it'll be delivered.  Right now device tree can only be
> used on SPARC, PowerPC and (I beleive) some x86 platforms.

MIPS and Microblaze too plus out-of-tree NIOS.

Regardless, I agree 100%.  This isn't (er, shouldn't be) a device tree
debate.  The problem does need to be solved for existing platforms.

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