From owner-freebsd-arm@freebsd.org Tue Sep 26 18:04:51 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 6E7C1E127BC for ; Tue, 26 Sep 2017 18:04:51 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 983EF6FC2D; Tue, 26 Sep 2017 18:04:50 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id c2f8b32b; Tue, 26 Sep 2017 20:04:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=UisIo37r4z9/rytGOky1H7SRZks=; b=kKfUrDwYuLooktcCjdXbO3RXxzSd xCd6BRNMl2/RanD6mGFF0YzqLE5G9JCral+VaU4vTNSZ5xvRMN8ApokZ1JYf9sga 59FiZsypZl1VNgzchvR5pvbdKobTRwbYViPdAuNG7bMTBoMb4mePKe45VE+c9lX/ I1WF/CDe2SURg/0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=SWGvOIcJJqlABHZWpmnVnKyOxNICm40AxD83aUmdwyWaQUZDBmwItLuk 6EuaXMDMFMHGPij+eYJF6mOsfzxJ6NSRShwMDVa7ayVbyVENJx3xFy7saLVC6jcR R4qwxtRPKcs3h9WlH+Z0GvX8ienBu/6waf0ZzXDTglKoiFTFUlc= Received: from knuckles.blih.net (ip-54.net-82-216-203.roubaix.rev.numericable.fr [82.216.203.54]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 70dfe1b4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 26 Sep 2017 20:04:47 +0200 (CEST) Date: Tue, 26 Sep 2017 20:04:46 +0200 From: Emmanuel Vadot To: Brett Glass Cc: Ian Lepore , 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> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:04:51 -0000 On Tue, 26 Sep 2017 11:32:21 -0600 Brett Glass 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