linux-kernel - Re: kbuild now support arch/$ARCH/include

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: <Pine.LNX.4.64.0807310916430.10810@anakin>
Date:	Thu, 31 Jul 2008 09:17:58 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Paul Mundt <lethal@...ux-sh.org>
cc:	David Howells <dhowells@...hat.com>, Arnd Bergmann <arnd@...db.de>,
	Greg Ungerer <gerg@...pgear.com>,
	Sam Ravnborg <sam@...nborg.org>,
	linux arch <linux-arch@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>,
	uClinux list <uclinux-dev@...inux.org>
Subject: Re: kbuild now support arch/$ARCH/include - time for ARCHs to convert

On Thu, 31 Jul 2008, Paul Mundt wrote:
> On Wed, Jul 30, 2008 at 02:26:04PM +0200, Geert Uytterhoeven wrote:
> > On Wed, 30 Jul 2008, David Howells wrote:
> > > Arnd Bergmann <arnd@...db.de> wrote:
> > > 
> > > > I think the more interesting aspect in m68knommu is what happens
> > > > when asm-m68k gets moved. Does that work as well?
> > > 
> > > Can m68knommu be merged into m68k and be made contingent on CONFIG_MMU?  This
> > > is what FRV does.
> > 
> > Sure it can ;-)
> > 
> > Actually I did a bit of work to add nommu support to m68k to make it
> > boot on old MMU-less Amigas, but it dates back to the 2.6.8.1 era...
> > 
> > The bigger issue is in those parts that are done differently by m68k and
> > m68knommu (esp. head.S).
> > 
> > Who's gonna take the work? :-)
> > 
> This sort of merging is fairly easy to do incrementally, at least by
> someone that has both platforms available. An easy first step would be to

Indeed. I have none of the currently supported m68knommu platforms,
though.
Don't know about Greg and m68k platforms (of course he can use ARAnyM
;-).

> move the m68knommu stuff that are implemented differently over as _nommu
> files, similar to how the _32/_64 renames happened, and then set about
> converging the two little by little. This is what I've been doing with
> sh64->sh integration for example, despite fundamental differences like
> having a totally different register layout and instruction set.

IC.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/