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: <1208331959.6958.272.camel@pasglop>
Date:	Wed, 16 Apr 2008 17:45:58 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	monstr@...nam.cz
Cc:	Arnd Bergmann <arnd@...db.de>,
	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 Wed, 2008-04-16 at 08:24 +0200, Michal Simek wrote:
> Hi Ben,
> 
> >> 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.
> 
> I think so. Sharing code among archs looks nice and this way is definitely
> right. But starting with communication with PowerPC guys that this code I want
> to use in case that this code is not in vanilla. This is not good start for
> doing this.
> I think if Microblaze will be in vanilla we can talked about separation MB and
> PPC part to kernel folder and shared code move to shared folder.

Well, LMB code is moving to generic anyway... So we may as well move
more stuff there ;-)

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