From owner-freebsd-arm@freebsd.org Fri Aug 11 05:22:49 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 0B0EEDB78C3 for ; Fri, 11 Aug 2017 05:22:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C26E112AD for ; Fri, 11 Aug 2017 05:22:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id g35so16636217ioi.3 for ; Thu, 10 Aug 2017 22:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=YSg36A5k3F0XfZ0Y3uaklzqYYIqkJ7W0NGH7yPzByrM=; b=sEXJwsn8JNANq3e5A0PVOjmyTD4y01EFoiRb0RxALfggxtwKRLEdm3JGXMwg8HL3vR vwu06HiR1gcvl+vAXye6Uzb7n/uY4yaMqBnoZinuvdCENBNvnBmtSnGZvkWIcj+f+xIX 2H4e/4OB1NUaHot7LTs/PuyHlXPILElyDiPNwuOcIrlpoMwG+N4WCxfAanofZZqT7XOA oE2ceaEHqjE5Bq5Y09Y9KL+WbL01lrea3itjvIGe04GLjyW4Ml2LuSUph65y5FB7H8SS UCehQ2sMU5FlnoLMpUveP8DxP/bBsfOoYHjdEw7O2Eb2I6uB7NyVENN4/Xi5aKd6TPuE MD4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=YSg36A5k3F0XfZ0Y3uaklzqYYIqkJ7W0NGH7yPzByrM=; b=Xh0mmdDiSK99/ZkF7WOSVde6PAXAs9lanXSEkHQkBKxeGXpbgRYQB119aBJei6DvUO bxc6Z4j/qcfpdPRlDRM+bTiukyT7Yy6TCa2JZbaX6a88zojqvD3q3prFyMwEt2YkMq+b TvSiYm6EDIZXHXgqodlkrsmwi63XbWmERhcRqZBlrkpF6PcMvLtdTfNJ+qeJTvpCHST+ vYNMMNs5n+BE61KgBHvmkBW8hzxg6Bm4ZZv+2z14z6cAb/o7i2glOzem/SH3mh6rlSvm TVNoUcXVZx57fzo8IDXLAgTKLGODsH9kvQzBghchEA2FpoOu6Y+TrU+M+bF9st6w5YNS qG5w== X-Gm-Message-State: AHYfb5g27xGoIA78tXaHVsPZBEyEULXi520cMkLxd/oR5kahYuh05c7z /NjHIjOf6F8K5rxsLianBEFa0RDEoZa+ X-Received: by 10.107.136.104 with SMTP id k101mr11753526iod.62.1502428967567; Thu, 10 Aug 2017 22:22:47 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Thu, 10 Aug 2017 22:22:46 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:fc73:9056:67a0:a7d0] From: Warner Losh Date: Thu, 10 Aug 2017 23:22:46 -0600 X-Google-Sender-Auth: 2tZ1xD69zVlvKpNvXVvIQ2VtxAU Message-ID: Subject: New Arch: armv7 To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Fri, 11 Aug 2017 05:22:49 -0000 As discussed here in June, we're creating a new arch. I've landed on the armv7 name (as opposed to earmv7hf or armv7l) for the following reasons: 1. armv7 isn't a huge amount of work to implement in our tree, while the other two names require substantially more complicated .if statements in makefiles. 2. Neither of the other names actually buy us a large amount in the ports. Autoconf is split and many other ports do different things to get the system they are running on and wouldn't benefit from the other names. There's a small number of ports that might be better, but not enough to justify the extra work in base. 3. It's more like the names we've been using, and won't cause confusion with our user base. And it will be easy enough for outsiders to see what we support from it without needing the decoder ring for NetBSD, or dealing with 'what's the trailing l mean, why doesn't armv6 have it, or arm and what about armeb' all the time. btw, if we ever do a big endian port, armv7eb will be the name, per project tradition. So, I'll be finalizing FCP-0100 with this data (I've sent the pull request) and will get an implementation together (I have the start of one I was able to knock out in about an hour, after spending twice that on the other two choices w/o reaching completion) and if there's issues that arise as we move forward, cope with them on the way to asking core to vote to bless this is the consensus of the relevant parts of the community. I hope to have it committed by the end of the month, and hope that the FCP process won't unduly delay things. Warner