From owner-freebsd-arm@FreeBSD.ORG Sat Mar 2 23:20:57 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DCBADDFF for ; Sat, 2 Mar 2013 23:20:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ia0-x236.google.com (mail-ia0-x236.google.com [IPv6:2607:f8b0:4001:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id 96E748F4 for ; Sat, 2 Mar 2013 23:20:57 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id w21so1806779iac.27 for ; Sat, 02 Mar 2013 15:20:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=R3L3KZCDLLkmIUetmWxNUkCDR5mxQuAUbrSJVuFrc0E=; b=PMW4X2qYdKNkaSpuH9ENJq+/XWog6whJ0tOCzHncq11be4aK4RMHN7edCv2SoHru6F HBdBe2sYVU/l91agNS6gbB9sBzISalO8Tto3Tc6KfZGGrS11/XtW155gyaThh4BNs7/V fbb+nh90B/IXUFC2lT63G2i2iriGu6h9XocqMTL5siXK+qHOTjoOyFZNjFzRAoEAts/O QB2/lYV1sPOwNbDNNFqTp9wKN9IB0mhGD01Fek4nQsuHsLQwtoHv872koJXYVwQkEimJ 5S8dVm1/VlUE9gb1oIO3oMyLJ2QPfYEtO12SUrm0/KwG4jC1K5SAKYwr1cUHK68GqQHh /g4Q== X-Received: by 10.42.126.133 with SMTP id e5mr17469452ics.17.1362266456949; Sat, 02 Mar 2013 15:20:56 -0800 (PST) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id ua6sm3990671igb.0.2013.03.02.15.20.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 02 Mar 2013 15:20:56 -0800 (PST) Sender: Warner Losh Subject: Re: About board-specific files.* Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Warner Losh In-Reply-To: Date: Sat, 2 Mar 2013 16:20:54 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <58FF3A9F-2782-429F-BE82-27728E8D209D@bsdimp.com> References: To: Tim Kientzle X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQm+j9bkC7jQQa7XP5s+MG2UW2MVkYd4c7D6sig657xr25ienKs9lKCgPXFbyFuhg+v9gdFa Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 23:20:57 -0000 On Mar 2, 2013, at 2:05 PM, Tim Kientzle wrote: > Now that I think I understand some of the issues in building > a GENERIC arm kernel, I'm starting to piece together > a kernel that has both RPi and BBone bits that I can > use as a testbed. >=20 > Next Problem: A lot of the boards are using > board-specific files.* to control what files get > linked into the kernel. >=20 > This seems like a real problem for a GENERIC kernel, > so I propose merging them into sys/conf/files.arm. >=20 > Here's how I'm doing it right now for my current > experiments. If anyone has a better idea, I'm > definitely interested. >=20 > Basically, I'm using "device bcm2835" to represent > all of the basic support for that particular SoC. > (An SoC is, after all, just another piece of hardware.) >=20 > Then the files marked "standard" in > arm/bcm2835/files.bcm2835 move to > files.arm as "optional bcm2835". >=20 > With this approach, the GENERIC arm kernel will > list the SoCs as devices: >=20 > device bcm2835 > device am335x > device omap4 > =85 etc =85 >=20 > That will bring in the basic support for those SoCs > (e.g., interrupt handler, gpio, clock management, etc). > Additional drivers (SDHCI, UART, USB, etc) will > be separate devices. >=20 > I think this makes sense, but I'm open to other ideas. I think this is perfect. It is what atmel uses to bring in different = atmel things. I don't think there are any atmel files specified as std = any more, and if there are they could transition to this. I know this = isn't an issue for a GENERIC for armv6, since there is not way an armv4 = and an armv6 kernel could be built today... Warner=