From owner-freebsd-arm@freebsd.org Sun Jul 14 18:09:15 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E9569A1BA4 for ; Sun, 14 Jul 2019 18:09:14 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB70A81C09 for ; Sun, 14 Jul 2019 17:28:20 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 76CF91FCD3; Sun, 14 Jul 2019 17:28:19 +0000 (UTC) Date: Sun, 14 Jul 2019 17:28:17 +0000 From: Mark Linimon To: Dennis Clarke Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD 11.3-RELEASE and 11.2-RELEASE images fail to boot on BeagleBone Black Message-ID: <20190714172816.GA26897@lonesome.com> References: <8352f841-0522-9f45-148d-d2948e97857e@gmail.com> <20190713152404.GJ1503@dendrobates> <6b3dcec02b425a8559605b4e6c5ada19ee642728.camel@freebsd.org> <20190713194256.GK1503@dendrobates> <85e35455-793a-84fe-c8cf-39b89ade7c11@gmail.com> <26864b34-624a-075f-4a10-859314649d2f@blastwave.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26864b34-624a-075f-4a10-859314649d2f@blastwave.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: AB70A81C09 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-1.81 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.959,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-0.25)[ip: (0.03), ipnet: 18.220.0.0/14(0.14), asn: 16509(-1.34), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.97)[-0.967,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.33)[-0.327,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2019 18:09:17 -0000 On Sun, Jul 14, 2019 at 04:19:37AM -0400, Dennis Clarke wrote: > I have the same issue with ppc64 and most certainly for RISC-V where > we are really well and truely in outer darkness. I don't understand. Can you explain this to me more clearly? fwiw, I have personally invested a lot of time in getting our powerpc64 documentation up to date on the wiki. As well: blackbird1% uname -a FreeBSD blackbird1.lonesome.com 13.0-CURRENT FreeBSD 13.0-CURRENT r349478 GENERIC powerpc blackbird1% uptime 5:25PM up 12:52, 2 users, load averages: 0.01, 0.05, 0.0 (It would have been up longer but I moved it into my rack.) What have I missed? As for RISC-V, IIUC, support for the architecture is very much in an alpha state. mcl