From owner-freebsd-arm@freebsd.org Tue Sep 26 18:22:07 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 675A1E153DE for ; Tue, 26 Sep 2017 18:22:07 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from nov-007-i577.relay.mailchannels.net (nov-007-i577.relay.mailchannels.net [46.232.183.131]) (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 078DE70B34 for ; Tue, 26 Sep 2017 18:22:04 +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 2725C20752D for ; Tue, 26 Sep 2017 18:22:00 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.147.85]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 922F9207878 for ; Tue, 26 Sep 2017 18:21:59 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.55.158]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Tue, 26 Sep 2017 18:22:00 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Spicy-Decisive: 19bd40563d222e7c_1506450120006_3568330493 X-MC-Loop-Signature: 1506450120006:4163123015 X-MC-Ingress-Time: 1506450120005 X-MHO-User: 92ef91b8-a2e7-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 92ef91b8-a2e7-11e7-a893-25625093991c; Tue, 26 Sep 2017 18:21:55 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8QILrCp001654; Tue, 26 Sep 2017 12:21:53 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1506450112.73082.143.camel@freebsd.org> Subject: Re: CUBOX snapshots working? From: Ian Lepore To: Emmanuel Vadot , Brett Glass Cc: freebsd-arm@freebsd.org Date: Tue, 26 Sep 2017 12:21:52 -0600 In-Reply-To: <20170926200446.c188fda613df2ffb894b1ff3@bidouilliste.com> References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> <201709261732.LAA21422@mail.lariat.net> <20170926200446.c188fda613df2ffb894b1ff3@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 18:22:07 -0000 On Tue, 2017-09-26 at 20:04 +0200, Emmanuel Vadot wrote: > On Tue, 26 Sep 2017 11:32:21 -0600 > Brett Glass wrote: >=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. You seem to be implying that this is another problem caused by switching from vendor-specific to mainline uboot. =A0I'm not sure that's the case here, but if it is, be clear: =A0It is purely a freebsd problem, because it was purely our choice (not mine) to switch from something that worked to something that doesn't. -- Ian > >=20 > > At 08:21 AM 9/26/2017, Ian Lepore wrote: > >=20 > > >=20 > > > I just DLed and booted that snapshot on my Cubox-4i without any > > > problems.=A0=A0As near as I can tell, the only difference is you've > > > got the > > > dual-core chip and mine has the quad. > > >=20 > > > The same u-boot should work for both.=A0=A0At least, that was the > > > case when > > > using the vendor-provided u-boot; the images are now built from > > > mainline u-boot.=A0=A0The output you provided does show that it > > > detected > > > the right kind of chip and amount of ram, so I think it should > > > support > > > both flavors of cubox. > > >=20 > > > -- Ian > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.o > > rg" >=20