From owner-freebsd-arm@freebsd.org Tue Sep 26 17:43:25 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 885C7E11D36 for ; Tue, 26 Sep 2017 17:43:25 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 4E26F6EEC0; Tue, 26 Sep 2017 17:43:24 +0000 (UTC) (envelope-from brett@lariat.net) Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id LAA21422; Tue, 26 Sep 2017 11:32:29 -0600 (MDT) Message-Id: <201709261732.LAA21422@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 26 Sep 2017 11:32:21 -0600 To: Ian Lepore , freebsd-arm@freebsd.org From: Brett Glass Subject: Re: CUBOX snapshots working? In-Reply-To: <1506435673.73082.129.camel@freebsd.org> References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 17:43:25 -0000 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. --Brett Glass At 08:21 AM 9/26/2017, Ian Lepore wrote: >I just DLed and booted that snapshot on my Cubox-4i without any >problems. As near as I can tell, the only difference is you've got the >dual-core chip and mine has the quad. > >The same u-boot should work for both. At least, that was the case when >using the vendor-provided u-boot; the images are now built from >mainline u-boot. The 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. > >-- Ian