public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: [uClinux-dev] ltib vs uclinux-dist
Date: Wed, 02 Sep 2009 22:24:04 +1000	[thread overview]
Message-ID: <4A9E63E4.9090803@snapgear.com> (raw)
In-Reply-To: <200909011134.13102.sfking@fdwdc.com>

Hi Steven,

On 09/02/2009 04:34 AM, Steven King wrote:
> On Tuesday 01 September 2009 04:52:06 Philippe De Muyter wrote:
>
>>> Longer term I think we need to fully merge m68k and m68knommu
>>> before we push any MMU ColdFire patches to mainline.
>>
>> I fully agree with that.
>>
>> Who is currently working on the m68k/m68knommu merge ?
>> Is there a mailing-list, website or other network resource about that ?
>> The arch trees of m68k and m68knommu have different structures.  What will
>> the structure of the merged tree look like ?
>
> I've been looking at this, and while I dont have anything ready yet, it doesnt
> seem too difficult.
>
> m68knommu/configs and platform can be merged directly into m68k; its the files
> in kernel, lib and mm and especially the m68k Kconfig and Makefile that require
> some effort.  The trivial approach would be to do some thing similar to what
> was done for the include files: append a suffix of _no to the m68knommu version
> of the file and _mm to the m68k version and then have a wrapper that uses
> #ifdef __uClinux__ to select between the two.

You want to use CONFIG_MMU as the decider in most situations.
The exception is header files that will be used outside of the kernel.

But otherwise yes, we could do a dumb merge and then clean up.


> Of course that doesn't gain us much, except once we then fixup Kconfig and
> Makefile and have a working build, we can then incrementally merge each of the
> files in kernel, lib and mm while testing with a working build.

It hasn't worked out too bad from my point of view in the header
file merge. Initially there was a lot of separate files, but wihtout
too much effort I have that done to only a dozen or so now.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      parent reply	other threads:[~2009-09-02 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090812194002.GA2309@frolo.macqel>
     [not found] ` <4A9D0350.9050402@snapgear.com>
     [not found]   ` <20090901115206.GA12946@frolo.macqel>
2009-09-01 18:34     ` [uClinux-dev] ltib vs uclinux-dist Steven King
     [not found]     ` <200909011134.13102.sfking@fdwdc.com>
2009-09-02 12:24       ` Greg Ungerer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9E63E4.9090803@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=uclinux-dev@uclinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox