From owner-freebsd-arm@FreeBSD.ORG Fri Feb 28 13:42:51 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71F3C94D for ; Fri, 28 Feb 2014 13:42:51 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 463421C76 for ; Fri, 28 Feb 2014 13:42:50 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WJNiD-0008cQ-VU for freebsd-arm@FreeBSD.org; Fri, 28 Feb 2014 13:42:50 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s1SDgkJw042113 for ; Fri, 28 Feb 2014 06:42:46 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+vxPRXrbyIAgsxZEc7JjRw Subject: A unified imx6 kernel config, old WANDBOARD-* configs going away From: Ian Lepore To: freebsd-arm Content-Type: text/plain; charset="us-ascii" Date: Fri, 28 Feb 2014 06:42:46 -0700 Message-ID: <1393594966.1149.161.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 13:42:51 -0000 I've added a new imx6 unified kernel config named IMX6. It has no compiled-in fdt, and can boot all three flavors of Wandboard when u-boot and ubldr load a dtb file. Folks should start using it and eventually the WANDBOARD* configs will go away when nobody needs them anymore. I build ubldr to load at address 11000000 and let it load the kernel at 12000000. (The kernel can load on any 1MB boundary, but ubldr doesn't make use of that feature yet.) ubldr will take a dtb file loaded by u-boot and pass it along to the kernel. Another option is to put the .dtb file in your /boot/kernel or /boot/modules directory, and ubldr will load it from there, using the filename set in the u-boot env var fdt_file. Unfortunately we can't do a single image that boots any wandboard, because u-boot itself has to be different for each board. This is what my u-boot env looks like on each wandboard: => printenv baudrate=115200 bootcmd=run ubnet bootdelay=1 console=ttymxc0 fdt_file=wandboard-dual.dtb loadaddr=11000000 loaderdev=net ubmmc=fatload mmc 0 ${loadaddr} ubldr; bootelf ubnet=dhcp ${loadaddr} /wand/boot/ubldr;bootelf Environment size: 265/8188 bytes The only thing that differs per-board is the fdt_file setting, and the u-boot binary itself. The "loaderdev=net" variable tells ubldr to load the kernel from the network device rather than disk. So now all my different model wandboards boot the same kernel and run from the same nfs root directory. -- Ian