From owner-freebsd-arm@freebsd.org Thu Apr 21 22:03:34 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51F3CB177FB for ; Thu, 21 Apr 2016 22:03:34 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from erouter6.ore.mailhop.org (erouter6.ore.mailhop.org [54.187.213.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3309B14E3 for ; Thu, 21 Apr 2016 22:03:33 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d7768f7d-080c-11e6-b8f9-33a5b3560672 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 21 Apr 2016 22:03:12 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u3LM3USj042490; Thu, 21 Apr 2016 16:03:30 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1461276209.1191.26.camel@freebsd.org> Subject: Re: Orange Pi One From: Ian Lepore To: Milan Obuch , freebsd-arm@freebsd.org Cc: Emmanuel Vadot Date: Thu, 21 Apr 2016 16:03:29 -0600 In-Reply-To: <20160421231326.1bf9a11f@zeta.dino.sk> References: <20160413232414.3a37907e@zeta.dino.sk> <20160414062820.7b907ba9@X220.alogt.com> <20160414064405.202e4eef@zeta.dino.sk> <20160418094916.10dc9ae8@zeta.dino.sk> <20160418174918.33d3d19e4105eb737d17b122@bidouilliste.com> <20160418210108.4047c526@zeta.dino.sk> <20160419092012.0ad4ad2d@zeta.dino.sk> <20160419093408.2f6d8d6472b09298f1e08ecb@bidouilliste.com> <20160419095358.351c74b3@zeta.dino.sk> <1461075584.1232.13.camel@freebsd.org> <20160419170932.3fe2b709@zeta.dino.sk> <20160421220125.00286858@zeta.dino.sk> <20160421224541.daec4614d2e5c88959a3d8e2@bidouilliste.com> <1461272263.1191.23.camel@freebsd.org> <20160421231326.1bf9a11f@zeta.dino.sk> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 22:03:34 -0000 On Thu, 2016-04-21 at 23:13 +0200, Milan Obuch wrote: > On Thu, 21 Apr 2016 14:57:43 -0600 > Ian Lepore wrote: > > > On Thu, 2016-04-21 at 22:45 +0200, Emmanuel Vadot wrote: > > > On Thu, 21 Apr 2016 22:01:25 +0200 > > > Milan Obuch wrote: > > > > > > > OK, so yesterday I solved this puzzle - it was stupid pilot > > > > error > > > > (my > > > > ubldr.bin was not built with fdt support), after fixing it I > > > > made > > > > a test today - building SD image from scratch. It is succesfull > > > > now, so > > > > it's time to do kernel hacking. u-boot-orangepi port needs some > > > > review > > > > and cleanup before submitting into port repository, but anybody > > > > interested could write me for more details. > > > > > > > > Regards, > > > > Milan > > > > > > FYI I've just commit support for pinctrl in my github repo > > > (along > > > with orangepi-one dts from uboot). > > > I'll look at SMP and USB this weekend. > > > > > > For the u-boot port, do not submit it. Uboot > 2015.04 cannot be > > > compiled with CONFIG_API and net support, this means no netboot. > > > I also have some port here : > > > https://github.com/evadot/u-boot-freebsd-port > > > I use the orangepi-pc port for my orangepi-one (orangepi-one > > > config > > > is commited in -HEAD uboot only). > > > > > > > Did you mean 2016.04? I'm doing netbooting on other (non > > -allwinner) > > boards with 2015.07 and 2015.10. > > > > If there is an older mainline uboot that does work right, or a > > vendor > > fork in a github repo, we can just use that in the port, there's no > > special reason to track the tip of the mainline uboot tree in our > > ports. > > > > -- Ian > > > > In my port I used 2016.01, AFAIK minimum with orangepi support. I > did not find any vendor uboot tree. Frankly I see not much use for > netboot for this kind of board - you must prepare micro SD with SPL, > uboot, ubldr, kernel and binaries, for netboot you would need SPL and > uboot... this still means micro SD. For any practical purpose I can > imagine boot from SD/MMC is just enough. > > Milan Nope, netbooting is not a feature to easily throw away. You may not need it, but imagine someone using a board as a distributed computing component. They might have a rack with literally thousands of units, and they're not going to want to update each sdcard individually; they'll have sdcards with just u-boot and ubldr that rarely need updating, and everything else will be nfs. -- Ian