From owner-freebsd-arm@freebsd.org Thu Jun 22 01:13:26 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 3FCD3D9CFC5 for ; Thu, 22 Jun 2017 01:13:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::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 0D28F2F2 for ; Thu, 22 Jun 2017 01:13:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id h134so5811610iof.2 for ; Wed, 21 Jun 2017 18:13:25 -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=1THpptkXjv4d9UY3D0g/QP2F+6clX9m8enKiC+1i6uE=; b=eXuT0RsXhxBaDOqjlNQw7dCRkH77VuwfAXegTegpl37JqEIHqtojNZL0Y+fAtbT5ps l3baoTDN4tXPhn/XqwcfflLRUHNfD9SdbfdhbJptajwU2rTZ6gbjLozYd4r8/voP2452 1Q92kdmDWq7cSZyZW+6kNHHrsX+uVf9VsZPdWARxtqo5uH+LUIRgUJtE34hqq7NEKQ4T 2m6FTuQi8T/t5YciqkLwzwrcjpZ09xqgHHcEgcthozGcVYDCAoasH6c1ikn07OKvNuc2 oTbr524A1l3rXjCokqPHcphbq+wWPscV/5DK278tFV444OFS/7a7KF7j9UN9eRw7ahvI umVA== 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=1THpptkXjv4d9UY3D0g/QP2F+6clX9m8enKiC+1i6uE=; b=bZtRbTp0+BGR71iWl3I5HLGOBAPHs+NOMniq8/XdrK7ymVJyedaehBtm2EZNZqzAc2 MoA8TTmVC3XUE5WuvcUinQ1FsKMe1ZO7OMmT4qEbLKUUo/uKABRYQq/sffgeCea3Vf7U pc9TJI/A8S7kK6wx/wL07v35IVEXefrDpRdfoH0FcY2tQadRQ8whQS6JfbdyvoFHrlAK Dhp1+yUXRqVlev9fD1Xiq03fDl16Zs92z0bmo0Wd36mGGqc06s+V1u8F5StZvMgCkoah sfSuNFYX5A7Mg4qV4mCzHnvoJ/BlzR87d+mu6pPgwDdy6nVPN9RMT0fShd44JsdNho3Y iFJA== X-Gm-Message-State: AKS2vOwt8PP8F7PS+t69L9nRL5kgeKwxxRepxYaIcuPphIkdmZ4wUy32 fkL6QnVQByXQOWUrPTe2Nxp2l6o8VuOo X-Received: by 10.107.16.217 with SMTP id 86mr40515ioq.134.1498094005125; Wed, 21 Jun 2017 18:13:25 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.192.69 with HTTP; Wed, 21 Jun 2017 18:13:24 -0700 (PDT) X-Originating-IP: [216.9.110.3] In-Reply-To: References: From: Warner Losh Date: Wed, 21 Jun 2017 19:13:24 -0600 X-Google-Sender-Auth: PnPVLL942fLJAAuaih8EtMFB-HI 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: Thu, 22 Jun 2017 01:13:26 -0000 On Sun, Jun 11, 2017 at 10:41 PM, Warner Losh wrote: > > > 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... > I've managed to get my old Atmel AT91SMA9G20 based board working, so I'm officially withdrawing this idea. I heard from a few people that had no issues with their armv5 boards and was wondering what I was talking about. I've found the root cause to my issues, so I think we're in good shape from a functional point of view. It looks like the unaligned issues that I'd seen in prior versions have been fixed at least since Feb of this year, maybe longer. As a side note, both the armv4 and armv6 busdma implementations work on armv4/5 hardware. Though the v6 implementation seems to use about 20-30% more memory in a quick test... Warner