Date: Tue, 26 Sep 2017 20:04:46 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Brett Glass <brett@lariat.net> Cc: Ian Lepore <ian@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: CUBOX snapshots working? Message-ID: <20170926200446.c188fda613df2ffb894b1ff3@bidouilliste.com> In-Reply-To: <201709261732.LAA21422@mail.lariat.net> References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> <201709261732.LAA21422@mail.lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Sep 2017 11:32:21 -0600 Brett Glass <brett@lariat.net> wrote: > 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 The problem isn't FreeBSD related, it's U-Boot related. You could test build mainline u-boot just to confirm that it isn't something due to our ports. > 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 > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170926200446.c188fda613df2ffb894b1ff3>