From owner-freebsd-arm@freebsd.org Tue Jun 13 01:04:07 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 9A1C7D88287 for ; Tue, 13 Jun 2017 01:04:07 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 38BFC26C6 for ; Tue, 13 Jun 2017 01:04:06 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 0abc58b2-4fd4-11e7-b96e-2378c10e3beb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 0abc58b2-4fd4-11e7-b96e-2378c10e3beb; Tue, 13 Jun 2017 01:03:00 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v5D12oME002268; Mon, 12 Jun 2017 19:02:50 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1497315770.81013.4.camel@freebsd.org> Subject: Re: Creating armv7 MACHINE_ARCH From: Ian Lepore To: Warner Losh , Russell Haley Cc: "freebsd-arm@freebsd.org" Date: Mon, 12 Jun 2017 19:02:50 -0600 In-Reply-To: References: <20170612152808.6094931.74364.27128@gmail.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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, 13 Jun 2017 01:04:07 -0000 On Mon, 2017-06-12 at 09:39 -0600, Warner Losh wrote: > Clearly, we woke up one day and realized Ian was right? And he's only been > saying it since pre R11 since that was the first release that supported it. > There was no armv6 support in 10. Ask a snarky question, get a snarky > answer... > > What's changed is that the port has gone from being mainly used by people > that had an rpi that supported a bunch of other platforms (including Ian's > iMX6) to a port that's used primarily by armv7 machines (including the > rpi2) that also happens to support the rpi (which is the only !armv7 > platform). When Ian started saying it, rpi was one of the better supported > platforms as well. Now with all the Allwinner support, improved iMX6 > support, and the rpi2 being armv7, we are now in a situation where most > users and most of the good support is on that platform. What's also changed > is Andrew's work on having a GENERIC kernel. We'd have a GENERIC one for > ARMv6 too: It's the RPI config :). > > Plus, we aren't quite doing what Ian wanted. He wanted a full rename. The > proposal on the able is to add an armv7 TARGET_ARCH in 12. Not to rename or > remove armv6. Sadly, that will still be there since the RPI foundation > keeps finding new ways to repackage the rpi into new boards that are just > too cheap to ignore. > > Warner > For the record... 1. Of course there was armv6 support in freebsd 10. 2. I never proposed eliminating armv6/rpi support, I was always about adding armv7 as its own arch.   I did once propose renaming armv6hf to armv6 without bothering to do the magic softfp compatibility thing you did, maybe that's what you're remembering (basically using tier-2 status freedom to break ABI in the middle of a released branch). Of course I support the new proposol to create an armv7 arch. :) -- Ian