From owner-freebsd-arm@freebsd.org Tue Sep 26 21:42:43 2017 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 77A41E22CB5 for ; Tue, 26 Sep 2017 21:42:43 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from crab.apple.relay.mailchannels.net (crab.apple.relay.mailchannels.net [23.83.208.42]) (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 302AC7C0DE for ; Tue, 26 Sep 2017 21:42:42 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 849258A709B for ; Tue, 26 Sep 2017 21:17:42 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.146.250]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id DFF3A8A88C7 for ; Tue, 26 Sep 2017 21:17:41 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.104.49]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Tue, 26 Sep 2017 21:17:42 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Plucky-Sponge: 77efe4191cc90469_1506460662357_2787366007 X-MC-Loop-Signature: 1506460662357:2416921812 X-MC-Ingress-Time: 1506460662357 X-MHO-User: 1dcdd18d-a300-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 1dcdd18d-a300-11e7-a893-25625093991c; Tue, 26 Sep 2017 21:17:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8QLHXbi001963; Tue, 26 Sep 2017 15:17:33 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1506460653.73082.156.camel@freebsd.org> Subject: Re: CUBOX snapshots working? From: Ian Lepore To: Russell Haley , Emmanuel Vadot Cc: freebsd-arm Date: Tue, 26 Sep 2017 15:17:33 -0600 In-Reply-To: References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> <201709261732.LAA21422@mail.lariat.net> <20170926200446.c188fda613df2ffb894b1ff3@bidouilliste.com> <1506450112.73082.143.camel@freebsd.org> <20170926204622.67ae9edbca62e2dcdbd1ea31@bidouilliste.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 21:42:43 -0000 On Tue, 2017-09-26 at 14:07 -0700, Russell Haley wrote: > On Tue, Sep 26, 2017 at 11:46 AM, Emmanuel Vadot om> wrote: > >=20 > > On Tue, 26 Sep 2017 12:21:52 -0600 > > Ian Lepore wrote: > >=20 > > >=20 > > > On Tue, 2017-09-26 at 20:04 +0200, Emmanuel Vadot wrote: > > > >=20 > > > > On Tue, 26 Sep 2017 11:32:21 -0600 > > > > Brett Glass wrote: > > > >=20 > > > > >=20 > > > > >=20 > > > > > One would think that sauce for the goose would be sauce for > > > > > the > > > > > gander. But is this particular Cubox now useless with > > > > > FreeBSD? > > > > > And if so, why? It is not an unusual model. The Cubox does > > > > > work > > > > > if I flash their "Ignition" startup software (which is used > > > > > to > > > > > bootstrap by downloading various OS images) to the same > > > > > Micro SD card. > > > > >=20 > > > > > --Brett Glass > > > > =A0The problem isn't FreeBSD related, it's U-Boot related. > > > >=20 > > > > =A0You could test build mainline u-boot just to confirm that it > > > > isn't > > > > something due to our ports. > > > >=20 > > > If we used to provide working cubox images and we don't anymore, > > > it's > > > hard to call that anything but a freebsd problem. > > =A0There is working cubox images, the last one is from yesterday. > > =A0You even say yourself that you did test it and that it worked. > > =A0Do we even know if the snapshot worked for this board ? > > =A0Brett, could you test the 11.0 release for example ? (I don't > > remember > > if for 11.1 we already switch u-boot or not). > I believe the change is in the u-boot port itself. However, I don't > think it's a u-boot problem (IMHO), it's a u-boot build configuration > problem. There are different board variants with different hardware > layout. u-boot has code for it, but our build does not account for. > Unless the scripts that build the 11.1 image use a different revision > of the u-boot port, wouldn't it just use the current 2017.7 base? >=20 > I'm trying to figure out how to generate a u-boot with the correct > SPL > portion of u-boot. One could pull the SolidRun u-boot repo, or go > find > the ports commit before the changeover and see if we can generate the > correct SPL. >=20 > I looked at Mainline u-boot and there is a board directory for solid > run. > https://github.com/u-boot/u-boot/blob/master/board/solidrun/mx6cuboxi > /mx6cuboxi.c > seems to support multiple memory configurations based on defines, so > this should just be a configuration problem. >=20 > We clearly need to start supporting the lower spec'd SolidRun boards > because this has come up a couple of times now since the changeover. > It should be just a matter of creating a port that does the same > thing > but generates the correct SPL file? My SOM is a i2eX so I can't be > too > much help (and I've also over volunteered myself!). >=20 > Russ >=20 The old imx6 uboot ports generated a single copy of uboot that would boot dual and quad-core versions of both hummingboard and cubox systems. =A0If the new uboot works only on quad core, that's another regression. =A0It might be possible to extract the u-boot.imx file from a freebsd 10 image to get back to the old one. Ooops. =A0Except it appears those no longer exist. -- Ian