From owner-freebsd-arm@freebsd.org Mon Jun 12 15:48:48 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 CB0DEBFEF8C for ; Mon, 12 Jun 2017 15:48:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 8E81B73DB5 for ; Mon, 12 Jun 2017 15:48:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id y77so57075043ioe.3 for ; Mon, 12 Jun 2017 08:48: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:in-reply-to:references:from:date:message-id :subject:to:cc; bh=PO8c2GpUnkcIMZf+dhkLvfSIDR0HjPiBPLcZJ0esWC0=; b=EtluRSml+OGeSxR0D+XrZIOfQXW+rSL7OxJePilPkXG8ySw9QYPX6FZntpu+AOzk3b X9PDGTcEJCj452ApzaOX/I3XyZ84l0YyWiFDOaP5pbWYc4omf5q8CItXDsif4tSpJX85 nkYFJ0IsvQh3Z277R8g7zROqhVV/IcLs0B9Q2y86WG3u9ULWZudukEN4zYx2Xuf0GHog Ru1LPp+4PdGhiMPsDF5uK4hqinifX7ZwErwD6HoJlBsbTNOT2koCDGw2O8SG/Q8UT9oa ut3hHWl8BC8lncyZA6jg6vyaEvYg6HVwg0tZNN1qv6yfOr6tKCTCdByEXptgSFozrtcT mrnQ== 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=PO8c2GpUnkcIMZf+dhkLvfSIDR0HjPiBPLcZJ0esWC0=; b=KKOMzjgtOIUnJUxPJAzWZDgnXV1dr200i8n8N1SKOSui39uorqplKSPaYii4Gd1MaX 4FtLnsEGGaf1C+n6GaZto/y/bW6Wfs0GzK28cc9xtM/PcHOMb+3aHwxpm6My/BqFapLR QdMBPv2xjvlJ0ptOiA9GD0TnpMOiVuoG1uBE9Yl4wguGQ/bogITGyObS6dIIeaaR8iGO 2rFx4lfvw9yetkVE8SORa3osQ9VUgFQS+JFr8rjnmGsvF4q+43dLyeMm39e4neAwOdsC JnhmjoY0l0CEJ/b6eg3RKz/orZDlraJR1tHJrPgOCboeY9YNFhHmghJopt19UCAl3QgA 2gMA== X-Gm-Message-State: AKS2vOza+xoB03SATp/hZQRm3n+1jdX6TfiD/ddGYcp5Rf9msxAT8Nvc 43ISglvhp3rbS+im0fBVAVJNekXgxg8s X-Received: by 10.107.170.213 with SMTP id g82mr35005758ioj.148.1497282527787; Mon, 12 Jun 2017 08:48:47 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.192.69 with HTTP; Mon, 12 Jun 2017 08:48:47 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:29a3:1710:671c:c6a7] In-Reply-To: <20170612154745.6094931.30709.27134@gmail.com> References: <20170612152808.6094931.74364.27128@gmail.com> <20170612154614.6094931.61931.27132@gmail.com> <20170612154745.6094931.30709.27134@gmail.com> From: Warner Losh Date: Mon, 12 Jun 2017 09:48:47 -0600 X-Google-Sender-Auth: mBqIJ4bRc8Q6Td_8ZZzYmo8NBQk Message-ID: Subject: Re: Creating armv7 MACHINE_ARCH To: Russell Haley Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 15:48:48 -0000 Me too: offence &=3D ~(TAKEN | INTENDED); :) On Mon, Jun 12, 2017 at 9:47 AM, Russell Haley wrote= : > Ha ha I should have used a bitwise or in that. > > Sent from my BlackBerry 10 smartphone on the Virgin Mobile network. > *From: *Russell Haley > *Sent: *Monday, June 12, 2017 8:46 AM > *To: *Warner Losh > *Cc: *freebsd-arm@freebsd.org > *Subject: *Re: Creating armv7 MACHINE_ARCH > > No offense meant, no offense take: glad for a passionate answer! > > Russ > > Sent from my BlackBerry 10 smartphone on the Virgin Mobile network. > *From: *Warner Losh > *Sent: *Monday, June 12, 2017 8:39 AM > *To: *Russell Haley > *Cc: *freebsd-arm@freebsd.org > *Subject: *Re: Creating armv7 MACHINE_ARCH > > Clearly, we woke up one day and realized Ian was right? And he's only bee= n > saying it since pre R11 since that was the first release that supported i= t. > 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 supporte= d > 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 chang= ed > 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 > > On Mon, Jun 12, 2017 at 9:28 AM, Russell Haley > wrote: > >> Sorry for the top post. >> >> Hasn't Ian Lapore been saying this since pre R10?=E2=80=8E I seems to re= member >> people doing backflips to get around this=E2=80=8E heading up to that re= lease and >> it was considered to much effort. Can I ask what has changed? >> >> Russ >> >> Sent from my BlackBerry 10 smartphone on the Virgin Mobile network. >> Original Message >> From: Warner Losh >> Sent: Thursday, June 8, 2017 1:27 PM >> To: freebsd-arm@freebsd.org >> Subject: Creating armv7 MACHINE_ARCH >> >> 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 wi= ll >> 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 i= s >> 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... >> >> Warner >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > > > >