From owner-freebsd-arm@freebsd.org Thu Jun 15 05:22:06 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 3A54DC0A1DD for ; Thu, 15 Jun 2017 05:22:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 00A3B6478C for ; Thu, 15 Jun 2017 05:22:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id m47so4407833iti.0 for ; Wed, 14 Jun 2017 22:22:05 -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=c7SDsGfQ3MIXNYe3UPGjsyzJexFpuKUdrfpzJEIjwNU=; b=JS7TgMgYHcQgKrqkmMeOVx/wBWEDO9h5vDvcMbx+k1pwiaJbmBbI0vHUk+FQDbgKbT 41608TO+rQUzfy1damuol4kuKB/2ZoHyb3r+ZPtB9XXcnUqf7k1MbTnaWbYzoEcyneC2 i8hgDT0jTEq9/8At8OE8TyLjXMsGvfVUqSb9O3jdzx3vPtEgFGxq9V/mz3/T8SFph+Tu Dtv4VIfFh1aB24VONWaBZ4W6VoRTqtMjjyD/1Z/r5OxaPGVG0XQ5u5YjZYWAj8QZN4Oo HtNOWW5pAVCQGZaL1eyWtczFCUmyeUYWNYnDzgAxAI3SSPkuCrJZd1iq+G6tWJQOECPE FmbQ== 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=c7SDsGfQ3MIXNYe3UPGjsyzJexFpuKUdrfpzJEIjwNU=; b=MsM7Ji85ohwhFhr1S1LAlLQVBmUlYnUbQbuPHBGMLKShfkIeH1rfsEt+e/8DszwV+A 0oK2aXcVpTnvj+Al9thVZ+eFaeGZZBgBasCCbxW+H2hCxs+4AJtTw5EYxEui6ooQocHj +vkw0Ry1Jf7q4ZC4aRWfk8aTxSKQH2zlksVlOi9jYFk3lsRekeH99UTHyJrEXeIM6k6F F9WXp950z7e1aLrmjJTVNd+gTHBqqVmkyc2IRNbJdiWxOmedgmFCCJDYp1hgbQ6OeXQp eD5PzEjR+qOJU74NUC4XJFe3CKHrfbr5ZyPUn1PRSEtcORgiHHr7HO7NDX/A/oeBZgh0 o8gA== X-Gm-Message-State: AKS2vOxVZd7vWceqcN9zPGilPcVdgXFOJnXRtFX3KOoBpLp41hCgNnJn kbECfat/uQFe0mM9Ej5gMBYkm8z8X6kC X-Received: by 10.36.20.211 with SMTP id 202mr3516272itg.103.1497504125193; Wed, 14 Jun 2017 22:22:05 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.192.69 with HTTP; Wed, 14 Jun 2017 22:22:04 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:402:51b7:c887:1fa6] From: Warner Losh Date: Wed, 14 Jun 2017 23:22:04 -0600 X-Google-Sender-Auth: GtH560ygrWJOP3yMCD4MDBlPriE Message-ID: Subject: Next up on creating armv7 MACHINE_ARCH: pre FCP stage To: "freebsd-arm@freebsd.org" , FreeBSD Release Engineering Team 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: Thu, 15 Jun 2017 05:22:06 -0000 On Thu, Jun 8, 2017 at 2:27 PM, Warner Losh wrote: > While the kernel doesn't really need an armv7 support, there will be a > better match to other systems if we create a armv7 MACHINE_ARCH. This will > be in addition to the armv6 MACHINE_ARCH we have today. This will allow us > to create a package set optimized for armv7 as well as armv6. While it is > true the RPI 1 is the only system that needs armv6 binaries, it's quite > popular and the Raspberry Pi folks keep creating new variants with the same > chip. It would also let us get the package stuff spun up and working before > we mess with armv6. > > This would also separate the fate of armv6 and armv7 support at a later > time, but the weak consensus I've heard appears to be that the time isn't > yet right to discuss retiring armv6 support... > I've created a new FCP for this. You can comment on it at https://github.com/freebsd/fcp/pull/6 but the FCP number may change since the allocation isn't official. I've created this on the belief that everybody here is either agnostic or fully supports this path. The FCP tries to enumerate the work and impact, but currently needs your help to flesh things out. I've done a first pass, but it's lame still. This is one of the first FCPs, so I'm going to use it a little as test case for the larger thing. There will be bumps. Feels may get bruised, but if so accept my apologies and help me do better in the future. I cc'd the re@ as a heads up that this may be coming down the pike and that discussions so far have been super hand-wavey on the RE@ side of things. I'd like to know what the actual impact will be so we can document it. At this stage, it's still in the draft stage and nothing is certain. This is my call for feedback, but call it 'pre-feedback' if I read FCP-0 wrong and am doing it wrong :) My gut tells me that to make my doc better, do it on the pull request. To raise serious issues that need to be discussed, reply to this message. To talk about the many flavors of Rpi, about unified releases, 32-bit ports to A-53, or any other odd tangents, please do that in arm@, but I'd humbly request a new subject. Comments? Warner