From owner-freebsd-arch@FreeBSD.ORG  Wed Feb 17 22:47:56 2010
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 38CB31065676;
	Wed, 17 Feb 2010 22:47:56 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id ECDD28FC0C;
	Wed, 17 Feb 2010 22:47:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1HMeOjW056121;
	Wed, 17 Feb 2010 15:40:24 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 17 Feb 2010 15:40:39 -0700 (MST)
Message-Id: <20100217.154039.1142818667055144394.imp@bsdimp.com>
To: attilio@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100216.135906.812628220523048669.imp@bsdimp.com>
References: <3bbf2fe11002151610l41526f55r5e60b5e46ce42b64@mail.gmail.com>
	<20100216.135906.812628220523048669.imp@bsdimp.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: arch@FreeBSD.org, emaste@sandvine.com
Subject: Re: [PATCH] Adding shared code support for ia32 and amd64 -- x86
 sub-branch
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2010 22:47:56 -0000

In message: <20100216.135906.812628220523048669.imp@bsdimp.com>
            "M. Warner Losh" <imp@bsdimp.com> writes:
: In message: <3bbf2fe11002151610l41526f55r5e60b5e46ce42b64@mail.gmail.com>
:             Attilio Rao <attilio@FreeBSD.org> writes:
: : There are few things to discuss. One, that I had not necessity to dig
: : about still, is about how to organize headers (include/). Maybe some
: : replication ala pc98 may be good.
: 
: Most of the pc98 replication these days is in the form of "#include
: <i386/foo.h>" and we install i386/include into /usr/include/i386 as
: well as pc98/include into /usr/include/machine.
: 
: I'm working in a similar vein.  For a while, one has had to specify
: TARGET_BIG_ENDIAN in order to build big endian MIPS or ARM binaries.
: This is lame.  I've eliminated it and have made it possible to build
: mipsel, mipseb, arm or armeb binaries by setting TARGET_ARCH to one of
: these, while still sharing all the mips code in one directory and all
: the arm code in another.

You can see the results of this work in
	http://people.freebsd.org/~imp/tbemd.diff

the patch is a little rough, and there's an issue with make universe
for mips kernels still that I need to track down[*], but otherwise it
looks good.

Warner

[*] Well, and a bigger, meta question: if we're building all the
kernels for a given MACHINE setting, and that MACHINE setting supports
both endians, how do we cope (short of putting back in the big endian
hacks I'm trying to eliminate).