From owner-freebsd-arm@FreeBSD.ORG Wed Sep 5 05:03:30 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4367D106566C for ; Wed, 5 Sep 2012 05:03:30 +0000 (UTC) (envelope-from gonzo@hq.bluezbox.com) Received: from hq.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id E85CF8FC0A for ; Wed, 5 Sep 2012 05:03:29 +0000 (UTC) Received: from [207.6.240.242] (helo=[192.168.1.64]) by hq.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1T97lQ-0001Wg-DL; Tue, 04 Sep 2012 22:02:58 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1463\)) From: Oleksandr Tymoshenko In-Reply-To: <6B74ADD7-3266-4919-BEB4-B10E0C1BAB58@kientzle.com> Date: Tue, 4 Sep 2012 22:03:01 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0DCAC001-FF06-431A-A486-2B50BE913B0D@bsdimp.com> <7E18623F-3945-4EA0-B332-5A5C717B20F0@kientzle.com> <9896AA3E-D8A0-4CE8-8160-4672AA07388F@cheney.net> <6B74ADD7-3266-4919-BEB4-B10E0C1BAB58@kientzle.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1463) Sender: gonzo@hq.bluezbox.com X-Spam-Level: ---- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-09-04, at 9:52 PM, Tim Kientzle wrote: > > On Sep 4, 2012, at 9:33 PM, Dave Cheney wrote: > >> Sorry to butt in on this discussion, but how feasible would it be to adapt this build script to the pandaboard. I understand there may be a config in svn similar to the beaglebone which may be applicable. > > I've started tinkering with ideas for generalizing my > BeagleBone script so it can build system images for > other boards. > > The issue isn't the FreeBSD kernel config but rather > juggling all the different pieces of boot machinery > and the various filesystem constraints. > > Still just noodling the idea around, but I think I've > got a few things to build on. For now, I'm limiting it to > just: > * ARM-based boards > * Building a disk image > > I only have a BeagleBone and a RaspberryPi at > the moment, so Pandaboard support would require > some help. At a minimum, I'd be interested in > an outline of what a Pandaboard image looks > like in terms of boot files, partitions, etc. [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Cc: arm@freebsd.org Subject: Re: Towards an ARM system-building script X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2012 05:03:30 -0000 On 2012-09-04, at 9:52 PM, Tim Kientzle wrote: >=20 > On Sep 4, 2012, at 9:33 PM, Dave Cheney wrote: >=20 >> Sorry to butt in on this discussion, but how feasible would it be to = adapt this build script to the pandaboard. I understand there may be a = config in svn similar to the beaglebone which may be applicable.=20 >=20 > I've started tinkering with ideas for generalizing my > BeagleBone script so it can build system images for > other boards. >=20 > The issue isn't the FreeBSD kernel config but rather > juggling all the different pieces of boot machinery > and the various filesystem constraints. >=20 > Still just noodling the idea around, but I think I've > got a few things to build on. For now, I'm limiting it to > just: > * ARM-based boards > * Building a disk image >=20 > I only have a BeagleBone and a RaspberryPi at > the moment, so Pandaboard support would require > some help. At a minimum, I'd be interested in > an outline of what a Pandaboard image looks > like in terms of boot files, partitions, etc. I think partition-wise it's pretty much the same - FAT partition=20 with boot loader and the rest is available for OS.=20 Boot partition should contain second-stage loader in file named MLO and the rest is up to this binary. I use MLO + u-boot combination. Here is article on boot process: http://elinux.org/Panda_How_to_MLO_%26_u-boot