From owner-freebsd-arm@FreeBSD.ORG Sat May 18 09:29:01 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 84D8BF3A for ; Sat, 18 May 2013 09:29:01 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from newton.metanet.ch (newton2.metanet.ch [80.74.158.131]) by mx1.freebsd.org (Postfix) with ESMTP id EA22A93E for ; Sat, 18 May 2013 09:29:00 +0000 (UTC) Received: (qmail 26216 invoked from network); 18 May 2013 11:28:53 +0200 Received: from 217-071-083-008.ip-tech.ch (HELO ?192.168.11.88?) (217.71.83.8) by newton.metanet.ch with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 18 May 2013 11:28:53 +0200 Message-ID: <519749D4.2070100@thieprojects.ch> Date: Sat, 18 May 2013 11:28:52 +0200 From: Werner Thie User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Port: U-Boot for BeagleBone References: <3B16A2E5-C92B-4248-BE98-DD5C1194CB05@freebsd.org> <86vc6hpb5r.wl%gnn@neville-neil.com> <8DC27DAB-FC30-4152-A408-4D666AD15875@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm 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, 18 May 2013 09:29:01 -0000 Hi all On 5/18/13 5:48 AM, Adrian Chadd wrote: > This makes it really difficult to potentially support building FreeBSD > images on non-FreeBSD platforms. Hmm, but wasn't that the case for a long time, I remember failing to do a full rebuild of FreeBSD on the Mac a year ago, after lots of hand waving and hair scrathcing. I gave in to do everything on VM's running FreeBSD for now. Although now with clang/LLVM in the picture on FreeBSD too, I would probably have a better time now > It also means that people can do things like have out of date builds > of things like bootloaders, mkuboot/mkuzimage, etc. At least all the parts you have to worry about are in one place, somebody has to look after the system in some way Werner > That's why I'm kind of a bit worried about this trend. > > I'm likely going to go the opposite way with my stuff. Ie, if I do > need bootloaders and such, I'll be packaging either the source trees, > or ports themselves, as part of the "freebsd-wifi-image" build > environment. I'll try to reuse the port build infrastructure as much > as possible but I won't rely on many tools and external support > software trees that aren't in /usr/src or the build environment > itself. > > Thanks, > > > adrian > > On 17 May 2013 16:01, Tim Kientzle wrote: >> >> On May 17, 2013, at 5:20 PM, Adrian Chadd wrote: >> >>> ... so how do I do a userland build of a bootloader? :-) >> >>> Does crochet have extra stuff in it to build ports with alternate >>> roots and install-as-user options set? Or does it now require you have >>> them installed before you can build images? >> >> This is still pretty experimental, so feel free to chime >> in with better ideas. >> >> My thinking right now is essentially that: >> >> * Port/package creates /usr/local/share/u-boot/u-boot-beaglebone/ >> * Crochet uses these files when it builds the image >> >> So yes, the port or package containing the boot bits >> would be a prerequisite. For the interim, this is not >> much worse than the current "you have to download >> the source and run crochet as root." >> >> This is basically driven from the observation that Crochet's >> current logic to build a boot loader contains essentially >> the same information (place to download source, patches, etc) >> that go into a FreeBSD port. So it avoids a chunk of duplication >> to make the boot loader builds be ports. >> >> I haven't thought through the non-root build case yet: >> >> Obviously, once the port/package is installed, using it >> as a non-root user is no problem. I suspect this is the >> common case. >> >> Building/installing the port as a non-root user should >> be feasible, but I haven't tinkered with that yet. >> >> Downloading/installing the package as a non-root user >> may also be feasible. >> >> Any suggestions? >> >> Tim >> >> >> >>> Thanks, >>> >>> >>> adrian >>> >>> >>> On 17 May 2013 14:08, wrote: >>>> At Fri, 17 May 2013 13:41:33 -0700, >>>> hiren panchasara wrote: >>>>> >>>>> On Fri, May 17, 2013 at 1:22 PM, Tim Kientzle wrote: >>>>>> I'm trying to move the actual building of boot loaders out of Crochet and into FreeBSD ports. >>>>>> >>>>>> Here's the first attempt at such a port (many thanks to Diane Bruce for patiently tutoring me through this): >>>>>> >>>>>> http://people.freebsd.org/~kientzle/u-boot-beaglebone.tgz >>>>>> >>>>>> I'd appreciate any feedback: >>>>>> * Can you build this? >>>>> >>>>> Yes. >>>>> >>>>> Its fetching things and I can see uboot generated in >>>>> work/u-boot-2013.04/ >>>> >>>> It claims to require a cross building compiler in /usr/obj so I'm >>>> waiting for that to build on my laptop. >>>> >>>>>> * Suggestions for improving it? >>>>>> >>>>>> If this works, I plan to use it as a template for U-Boot for other >>>>>> platforms (RaspberryPi, Pandaboard, etc.). Crochet would then >>>>>> rely on these ports instead of building boot loaders itself. Even >>>>>> better, these will eventually be built by the package system and >>>>>> available through packages. >>>>> >>>>> sweet! >>>>> >>>> >>>> Works for me. Thanks to both of you. >>>> >>>> Best, >>>> George >>>> _______________________________________________ >>>> freebsd-arm@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >