linux-mips
[Top] [All Lists]

Re: Embedded MIPS/Linux Needs

To: Joe deBlaquiere <jadb@redhat.com>
Subject: Re: Embedded MIPS/Linux Needs
From: Keith Owens <kaos@ocs.com.au>
Date: Mon, 26 Mar 2001 13:23:15 +1000
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@oss.sgi.com
In-reply-to: Your message of "Sun, 25 Mar 2001 21:01:52 CST." <3ABEB120.8020609@redhat.com>
Sender: owner-linux-mips@oss.sgi.com
You like long lines, don't you ;)  Reflowed for readability.

On Sun, 25 Mar 2001 21:01:52 -0600, 
Joe deBlaquiere <jadb@redhat.com> wrote:
>1. Would it be possible to lump some of the different MIPS variants
>together more closely? In my dream world I could build one kernel that
>would boot on every mips architecture. This way the work can be more
>general. As it stands now, if you want Tx39 or Vr41 variants you're
>working out of a different tree.

FWIW I am working on a Makefile rewrite for 2.5 which will help with
this problem.  Instead of one 120Mb kernel source tree for each
architecture, 2.5 will support logical kernel source trees and separate
source and object directories.  The logical source is built up from
base kernel code (Linus's tarball) plus zero or more layers that
contain additional or different code.  So you compile

2.4.x -> ix86 object directory
2.4.x + common mips -> common mips object directory
2.4.x + common mips + Tx39 -> Tx39 object directory
2.4.x + common mips + Vr41 -> Vr41 object directory

All use the same untouched 2.4.x tarball as the base.  You can compile
multiple targets from the same source at the same time, using different
object directories.  A change to base 2.4.x or to common mips is
automatically seen by all the object directories.


<Prev in Thread] Current Thread [Next in Thread>