From owner-freebsd-arm@freebsd.org Mon Jun 12 04:41:45 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 A025ABF3A88 for ; Mon, 12 Jun 2017 04:41:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 6C24E81A0F for ; Mon, 12 Jun 2017 04:41:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id k93so50663926ioi.2 for ; Sun, 11 Jun 2017 21:41:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LXEZGjhgSmudnsBZwLcWEPXV7LSvwWu9VPMnoVGY8eg=; b=hc2Ey7Fcf6ThJy8sHggKoogsRf24WtlbJrFWyoixdf3AIHNm6pzfOiZz/IkViXY8LL cKqScueZANDHpGMCy9vmzIYjT0u4Rgh16OvpGKnU+Qj1M7n5gTyLQuyi5nVKsgxM3f7K /KtipxaWhu/LqdogoNWJ8KAtXk/bMrcXqh4M21MEzm1wqAqKZM2jK27/pwsQiJBn4TrL 3uJhJgUIo85tvQBNSrROHC/bJT5DUhqQfBYnWn6jl0BukAsiYWX0EumCpO4BdLVfU5xx 79hMuTDQP1l8sJvI58S7Pe6rkyZvefkCk6o9AHmbpx1Oo2J552wIO+hRo++fIYc9OklY WHZg== 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:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LXEZGjhgSmudnsBZwLcWEPXV7LSvwWu9VPMnoVGY8eg=; b=s1DJdEnRYS+n2sehH02rjIjXviE+HkvT2ZOZfCjdLDJFxvZVBRlC0rIohmq/brLNmw cOqZh8HKSeAvAfHK0iydDF/ovKkgs5zGOAcuQbJMU732npzTZwGmMxfXFkAdSEr0JDkY 7OpbQQBxzBUFc9GHF67VlmIG9IBHkf7vg8/8V+5qd50fcSoq2MAnj1dtGDyDoA2XsTrO aB1JaL+8jfCqtKL6G0d7yWd4UvDhwLKnZvp/ykbfZzi+Wh7heHNXws7hkimAtQPmooFJ l6jTH8KHPxGiM6z5UmtnLBZNpG/PxfjloWHbRHVV95FlUX+s8Tn/AkHKpz8Qmpjutcw/ B5Cg== X-Gm-Message-State: AODbwcB3QWmJZzNG44chvnc92fCZlUvxijMAxKL2gQaPIB71kcCTabMK IxLh6I9SwGbWTadzYysG4qESeeN8ryLh X-Received: by 10.107.197.68 with SMTP id v65mr16914064iof.218.1497242504633; Sun, 11 Jun 2017 21:41:44 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.192.69 with HTTP; Sun, 11 Jun 2017 21:41:43 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:29a3:1710:671c:c6a7] In-Reply-To: References: From: Warner Losh Date: Sun, 11 Jun 2017 22:41:43 -0600 X-Google-Sender-Auth: jBRn9CsrhcAA3llQmHE7syIoS-M Message-ID: Subject: Re: Deorbiting armv4 and armv5 support To: Ronald Klop Cc: "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: Mon, 12 Jun 2017 04:41:45 -0000 On Sun, Jun 11, 2017 at 3:28 PM, Ronald Klop wrote: > On Thu, 08 Jun 2017 22:22:51 +0200, Warner Losh wrote: > > Greetings, >> >> The pmap in armv4/5 has been broken for years at this point. It basically >> works, but has issues with unaligned buffers. Since these have remained >> unfixed for a long time, and most of the main ARM developers have given up >> trying to fix it, I think it would be best to retire the support rather >> than waste people's time that seem to be working only to discover after a >> lot of effort that it's busted. >> >> Since the consensus at the FreeBSD developer's summit appeared to be >> 'let's >> let it go'. It would remove the TARGET_ARCH arm and armeb. armv6 would >> remain unaffected (though see a parallel thread). >> >> Warner >> > > What branches are you talking about? > I'm thinking only the -current branch. However, I'm thinking now that I'll write up something more formal (the FCP process) and start maybe a 3 month timeout. There's two leads on a fix, I'll be looking at one of them in the next few days. If one of these fixes is good, I'll merge it. The second one is a long shot, though... So, my current plan is that if it remains unfixed by, say Sept 1, 2017, I'll deorbit. I may adjust that date depending on the timing of the 12 branch, since I want to get this resolved before the branch... Warner