Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754854AbYGaHST (ORCPT ); Thu, 31 Jul 2008 03:18:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752891AbYGaHSF (ORCPT ); Thu, 31 Jul 2008 03:18:05 -0400 Received: from harold.telenet-ops.be ([195.130.133.65]:53152 "EHLO harold.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752637AbYGaHSD (ORCPT ); Thu, 31 Jul 2008 03:18:03 -0400 Date: Thu, 31 Jul 2008 09:17:58 +0200 (CEST) From: Geert Uytterhoeven To: Paul Mundt cc: David Howells , Arnd Bergmann , Greg Ungerer , Sam Ravnborg , linux arch , LKML , Linux/m68k , uClinux list Subject: Re: kbuild now support arch/$ARCH/include - time for ARCHs to convert In-Reply-To: <20080731032338.GA14296@linux-sh.org> Message-ID: References: <200807300907.25186.arnd@arndb.de> <20080728200500.GA14284@uranus.ravnborg.org> <48900EE4.8030606@snapgear.com> <3995.1217410495@redhat.com> <20080731032338.GA14296@linux-sh.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1997 Lines: 52 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 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@linux-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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/