From owner-freebsd-arch@FreeBSD.ORG  Mon Jan  9 13:48:27 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7DBD0106566B;
	Mon,  9 Jan 2012 13:48:27 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 52DE08FC15;
	Mon,  9 Jan 2012 13:48:27 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170])
	by cyrus.watson.org (Postfix) with ESMTPSA id 070D746B06;
	Mon,  9 Jan 2012 08:48:27 -0500 (EST)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
	by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8A814B967;
	Mon,  9 Jan 2012 08:48:26 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-arch@freebsd.org
Date: Mon, 9 Jan 2012 07:57:29 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; )
References: <CAJ-Vmom08uFV+NMryjZon_xnqo95MAK8r2=0s_JqRet7EMdn4g@mail.gmail.com>
	<DFFFE611-01A1-4B3F-8DFF-72E410483D5D@lassitu.de>
	<CAJ-Vmo=peK+A+TnLVRZvf0TVSnCBisXRRpKgV+pwC-qL3-PABQ@mail.gmail.com>
In-Reply-To: <CAJ-Vmo=peK+A+TnLVRZvf0TVSnCBisXRRpKgV+pwC-qL3-PABQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201201090757.29250.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
	(bigwig.baldwin.cx); Mon, 09 Jan 2012 08:48:26 -0500 (EST)
Cc: Adrian Chadd <adrian@freebsd.org>, Stefan Bethke <stb@lassitu.de>
Subject: Re: Where should I put ar71xx_* modules?
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: Mon, 09 Jan 2012 13:48:27 -0000

On Monday, January 09, 2012 4:04:14 am Adrian Chadd wrote:
> On 9 January 2012 00:52, Stefan Bethke <stb@lassitu.de> wrote:
> > We have lots of modules that have specific requirements; they're still 
connected to the build.  What warrants different handling here?  You could put 
them under .if ${MACHINE_CPUARCH} != "mips" like a number of them are already.
> 
> Hm, I didn't want to add modules for a specific SoC that won't ever be
> built for any other platform. Eg, if someone does a XLR build, they
> shouldn't get ar71xx modules built.

Were you planning on including them in the ar71xx kernel configs via 
MODULES_OVERRIDE or some such?  If so, that would be sufficient to get
'make tinderbox' to cover them at least (and hopefully tinderbox builds).
In that case I think it is fine to not have them hooked up in the main
sys/modules build.  Or rather, if Warner commits his KERNOPTS thing, perhaps
you could make sys/modules/Makefile include them on appropriate SoC kernels
only.

-- 
John Baldwin