From owner-freebsd-arm@FreeBSD.ORG Sun Feb 10 07:52:25 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 25B4E343 for ; Sun, 10 Feb 2013 07:52:25 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by mx1.freebsd.org (Postfix) with ESMTP id E67BBD8F for ; Sun, 10 Feb 2013 07:52:24 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o6so5268035oag.4 for ; Sat, 09 Feb 2013 23:52:24 -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=JR1rsVDGrrr5SP6/ABljDEpNfWM/IAtVNQGG8wdyWyM=; b=UahGjNloX+fjEGhZ5I1lcasiNFw6n+JBSDYzpL3OvOsh4qenquR8eQNJN1Rux29bEM CJ1QQc3dj8eKEX5oepVtxvLXZbziGidv4qUvFDlQPf8ZmvQBzzz3hyknC7vf95buGwgY 7JUH0GWj1Cr/p8wUh4z8VhJr67OlLq2rYrIvtBjRyIOwHDKF/wZJejtQ5G3zDWDTffLm aXpAd3alFR9bgzZTVRVMjYEIbFiig3VEvDYArfXTn0UuOkLDrjeraaQueMOYX8e4zv6R hz6PebqUA+tK2Bm2Baxk+6DOT+m74dcraJrNRU/o4SFXyv+2WnMhWBvAXKhVq+NIG8uc UW1A== X-Received: by 10.182.54.102 with SMTP id i6mr7923396obp.67.1360482744057; Sat, 09 Feb 2013 23:52:24 -0800 (PST) Received: from 53.imp.bsdimp.com ([209.117.142.2]) by mx.google.com with ESMTPS id k4sm45812954oeb.5.2013.02.09.23.52.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 09 Feb 2013 23:52:23 -0800 (PST) Sender: Warner Losh Subject: Re: building RaspPi Images Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20130210203222.6b51e505@bender> Date: Sun, 10 Feb 2013 00:52:16 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5116CB50.9080303@ceetonetechnology.com> <7757848F-45C6-4DEF-A4A2-5F900EB10A06@kientzle.com> <20130210012052.4d7e1a46@ivory.local> <58DCA6BE-8C06-4F69-81A2-A3582FBB5B12@kientzle.com> <20130210203222.6b51e505@bender> To: Andrew Turner X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQmZPl4y+vJIr8tzBFIywtv/F38YlWYsIU8TRty2wTPh3bv34829r+d+JrqBWSx4IwhCEzJO Cc: Tim Kientzle , freebsd-arm@freebsd.org, Brett Wynkoop 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: Sun, 10 Feb 2013 07:52:25 -0000 On Feb 10, 2013, at 12:32 AM, Andrew Turner wrote: > On Sat, 9 Feb 2013 23:03:38 -0800 > Tim Kientzle wrote: >=20 >> On Feb 9, 2013, at 10:20 PM, Brett Wynkoop wrote: >>>=20 >>> I was thinking that we should be able to generate a generic image >>> that will boot on both the Pi and the Bone. Maybe a config file >>> that includes the needed drivers for both boards. >>=20 >> I've thought about this and believe it is pretty routine, >> though I've not had time to actually try implementing it. >>=20 >> This specific combination is simplified by the fact >> that the boot bits are so different, so you can just >> put them all on the same SD card image. >>=20 >> There are a few pieces you'll need to work through: >> 1. An MSDOS partition with all the boot bits from both systems >> 2. A kernel with all of the drivers for both systems >> 3. ubldr will need to identify the board somehow >> 4. ubldr will need to obtain the correct FDT > 5. Update the kernel to allow it to be built for multiple boards. You > will need to at least fix: > - locore.S generates a fixed VA -> PA map, it's not too hard to fix > this, I've looked into it but don't have the time to get it into a > usable state. Aren't there also a number of VA/PA translations elsewhere that are also = hard coded via various #defines... > - initarm calls a number of functions that have are implemented on a > per SoC family case. FDT can help us here. We can get the SoC from it. > - Update the IRQ mask/unmask/next irq functions to allow multiple > implementations and pick the correct one on boot. > - Ditto for DELAY, DMA, reset, etc functions. I started on this at one point... > I would suggest the first step is to get a kernel that can boot on the > BeagleBone and PandaBoard. As they both have Ti CPUs they are similar > enough we could skip some of the items in my list as they are already > using a common SoC specific code base. I've also been pushing this for different Atmel boards as well, but = there isn't even FDT support for it just yet... Warner=