From owner-freebsd-arm@freebsd.org Wed Jun 8 19:30:08 2016 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 CD472B706D8 for ; Wed, 8 Jun 2016 19:30:08 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 A07681D49 for ; Wed, 8 Jun 2016 19:30:08 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5339F20C8F; Wed, 8 Jun 2016 15:30:07 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 08 Jun 2016 15:30:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= blackskyresearch.net; h=cc:content-transfer-encoding :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=NPpbD 47BZoSLhkUXZPErE+LtSuQ=; b=FKWdFYMM18C2GUymlRmHub/RFSH+g0fBduEC+ 3IoHtQjwkbcZLIBla2+mxX0BEtc2JT+JPDIi4mhwxoJL/E0cbeui3xEu51IcvJ07 NUU7GpIQaXhzBSIF2dxApZCsD4IMXeaPqlCk+ip6/lahvz3W85m3wUCJgpbs5Ybk 4+2t6k= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=NPpbD47BZoSLhkU XZPErE+LtSuQ=; b=KO36p0KBvSliHkTz8tKKhcgOLO54w7q8Fkr+bvZIQK3A2ar hzJYTFD0iKoT069ON7Owhh8rhZEOCU8vzeXKQXrdKKxMleFJFb/cEppZ7kLw1Js8 QkiWvZPaXGircNECjclpYN4HdizauSfHhpW1coOy7zeT2TqqdAf7n57HTC2c= X-Sasl-enc: DnBVzPCWgg2laVCPrzaDu8asMt15F6LZAf37d3XTU8aa 1465414207 Received: from [10.22.162.12] (unknown [66.111.12.42]) by mail.messagingengine.com (Postfix) with ESMTPA id 01934CCD26; Wed, 8 Jun 2016 15:30:07 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: RPI3 Hackathon at BSDCan/Dev SUmmit From: "Isaac (.ike) Levy" In-Reply-To: Date: Wed, 8 Jun 2016 15:30:06 -0400 Cc: Shawn Webb , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <8328C70D-51EA-4A0F-93A5-80CD665ECDFF@blackskyresearch.net> References: <20160607043134.GB22884@mutt-hardenedbsd> <20160607123450.GA75317@mutt-hardenedbsd> <20160608165711.GA63330@mutt-hardenedbsd> <20160608170107.GB63330@mutt-hardenedbsd> <20160608182810.GC63330@mutt-hardenedbsd> <0E28F6C5-96BC-4696-AD8F-C898CA0082D9@blackskyresearch.net> To: Russell Haley X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2016 19:30:08 -0000 Thanks Russ, All, > On Jun 8, 2016, at 3:22 PM, Russell Haley = wrote: >=20 > On Wed, Jun 8, 2016 at 11:56 AM, Isaac (.ike) Levy > wrote: >>=20 >>> On Jun 8, 2016, at 2:28 PM, Shawn Webb = wrote: >>>=20 >>> Your builds would be ARMv7, correct? As far as I know, there are no >>> ARMv8 BeagleBone boards. >>=20 >> Oh, I could be very mistaken- perhaps someone on list could help me = understand this- (searching the web isn't helping me here), >>=20 >> Can anyone on list here help me clarify the ARMv7 or ARMv8 = architectures? >=20 > Oh, oh, now you've done it... ha ha. This is very very very confusing > due to both marketing terms and some incongruency in terminology. I'm > just an amateur but I'm gonna take a shot at this so anyone who knows > better please feel free to correct me. >=20 > - Cortex-A8 is a marketing term for a specific processor design. This > is an "ARM Ltd." design that can be licensed by anyone. >=20 > - ARMv6, ARMv7 and ARMv8 are all different ARM *instruction sets*. > Different processors and families use different instruction sets (also > license-able by anyone to design their OWN processors). >=20 > - The Beaglebone series uses the Texas Instruments am33XX processor > family, which I think includes designs of both ARMv6 and ARMv7 > variants. The ARMv7 variants are based on the Cortex-A8 design. The > RPI2 uses a Broadcomm chip that is also a Cortex-A8 based processor > (ARMv7). >=20 > - Within FreeBSD, ARMv6 and ARMv7 are represented by one architecture > (ARCH) which is called ARMv6 (as was recently lamented by Mr. Lapore). > That's why you can't find reference to ARMv7. >=20 > (This is where i start getting fuzzy on details) >=20 > -The RPI3 is a 64 bit variant of the PRI development board. ARMv8 is > the Arm 64 bit family of instruction sets. In FreeBSD, it's called > AARCH64. That's why you won't see it mentioned as ARMv8. >=20 > Hence, when referring to RPI 1, 1+ 2 or 2B, the term armv6 is thrown > around and when discussing the RPI3 the term AARCH64 is used. >=20 > I think...? tee hee. >=20 > Cheers, >=20 > Russ "RISC architecture is gonna change everything." I really appreciate this shot at an explanation, and would hazzard to = say that clarity here is perhaps the biggest problem ARM platforms have = going for them :) For users, far more confusing than Itanium vs. AMD64 = ever was! Thanks again Russ. Best, .ike