Date: Tue, 4 Sep 2012 21:52:32 -0700 From: Tim Kientzle <tim@kientzle.com> To: Dave Cheney <dave@cheney.net> Cc: arm@freebsd.org Subject: Towards an ARM system-building script Message-ID: <6B74ADD7-3266-4919-BEB4-B10E0C1BAB58@kientzle.com> In-Reply-To: <9896AA3E-D8A0-4CE8-8160-4672AA07388F@cheney.net> References: <DD05E72B9F474BFE96B6A4B050D2A18A@gmail.com> <0DCAC001-FF06-431A-A486-2B50BE913B0D@bsdimp.com> <FAA208C1-2872-4BB6-A7EC-04C757533CA4@kientzle.com> <7E18623F-3945-4EA0-B332-5A5C717B20F0@kientzle.com> <9896AA3E-D8A0-4CE8-8160-4672AA07388F@cheney.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=20 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. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B74ADD7-3266-4919-BEB4-B10E0C1BAB58>