Re: kbuild now support arch/$ARCH/include - time for ARCHs to convert

[Greg Ungerer]

Geert Uytterhoeven wrote:
> 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@xxxxxxxx> 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
> ;-).

I don't have any real m68k (with MMU) hardware ;-)
I do have a v4e ColdFire with MMU, but that is not supported
by mainline m68k code. Maybe a help...


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

Probably not hugely difficult to merge together. Quite a few of the
m68knommu files came from m68k with only a little change and a lot
of removal. The board/platform stuff is obviously quite different -
very little (if any) commonality.

Just needs someone with time to sit down and do it and clean up
the resulting mess.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@xxxxxxxxxxxx
SnapGear -- a Secure Computing Company      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/