linux-kernel - Re: Microblaze Linux release

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

Message-Id: <1208296358.6958.237.camel@pasglop>
Date:	Wed, 16 Apr 2008 07:52:38 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	monstr@...nam.cz,
	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
	John Williams <john.williams@...alogix.com>,
	jwboyer@...ux.vnet.ibm.com, John Linn <John.Linn@...inx.com>,
	git-dev@...inx.com, Grant Likely <grant.likely@...retlab.ca>,
	git@...inx.com, microblaze-uclinux@...e.uq.edu.au,
	linux-kernel@...r.kernel.org, paulus@...ba.org
Subject: Re: Microblaze Linux release


On Tue, 2008-04-15 at 15:32 +0200, Arnd Bergmann wrote:
> 
> I'd recommend splitting prom.c into code that can be shared between powerpc
> and microblaze and architecture specific code. Anything that deals with
> LMB should go into powerpc, and you can simply use the alloc_bootmem
> mechanism for your architecture.

That is non trivial... the unflatten DT code among others relies heavily
on the LMB's to allocate the objects.

We could split the early accessors, unflatten code, and kernel-side
accessors at one point, though we already did most of it no ?

Ben.


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