From owner-freebsd-arm@FreeBSD.ORG Sat Mar 2 21:05:34 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DFFE7858 for ; Sat, 2 Mar 2013 21:05:34 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 869FE256 for ; Sat, 2 Mar 2013 21:05:33 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r22L5XtI060397 for freebsd-arm@freebsd.org; Sat, 2 Mar 2013 21:05:33 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id vdqdmqphfafjv2ri7m5ixjp77s; for freebsd-arm@freebsd.org; Sat, 02 Mar 2013 21:05:33 +0000 (UTC) (envelope-from kientzle@freebsd.org) From: Tim Kientzle Content-Type: multipart/signed; boundary="Apple-Mail=_C7E73846-5F7B-4D27-B3C6-E6592BD3BEBD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: About board-specific files.* Date: Sat, 2 Mar 2013 13:05:26 -0800 Message-Id: To: freebsd-arm@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) 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 21:05:34 -0000 --Apple-Mail=_C7E73846-5F7B-4D27-B3C6-E6592BD3BEBD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 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. Next Problem: A lot of the boards are using board-specific files.* to control what files get linked into the kernel. This seems like a real problem for a GENERIC kernel, so I propose merging them into sys/conf/files.arm. Here's how I'm doing it right now for my current experiments. If anyone has a better idea, I'm definitely interested. 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.) Then the files marked "standard" in arm/bcm2835/files.bcm2835 move to files.arm as "optional bcm2835". With this approach, the GENERIC arm kernel will list the SoCs as devices: device bcm2835 device am335x device omap4 =85 etc =85 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. I think this makes sense, but I'm open to other ideas. Tim --Apple-Mail=_C7E73846-5F7B-4D27-B3C6-E6592BD3BEBD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQEcBAEBAgAGBQJRMmmXAAoJEGMNyGo0rfFBRP4H/0yljEtP+/DSjXBRVA4Zeel7 mpedLt5ct+XzZuVyDaBcHkAVCzxJQy9JsmfoCv4FhYpnVxa9aXJ7db2n4bm/SyVN p2Tidsbvnsm9Cf0GaKQQV51rnKCvbuT4Qy3ZnJTmup4Z93OWJluh2zpE6EV6/vng 4VOhnOiwSeQbAql7nE0MIUZy2TNaWgxhcNMd7Ua7B3dpG7Jjxuiu2fMnpWtnaIfl /wYLBu7aad+3F5NE258P6TrAcmK/RJYYB5vgQP8joiFO3Na/6iDNOs0pMkGtUC/D qduy1NqOqL2eIu+Gn2LmcKC3uEv0d1Hw1Buf9mvbYRxJu5IJ8gDP+is8vSSOgqc= =oSfM -----END PGP SIGNATURE----- --Apple-Mail=_C7E73846-5F7B-4D27-B3C6-E6592BD3BEBD--