From owner-freebsd-arm@freebsd.org Sun Oct 15 18:12:55 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 A265BE481F9 for ; Sun, 15 Oct 2017 18:12:55 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 24F8081EBC; Sun, 15 Oct 2017 18:12:55 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id f4so30301761wme.0; Sun, 15 Oct 2017 11:12:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GgaA1p0fckS/xkVcv6xLVDzsEsvBNZIgKR6q+KUe7ZU=; b=lQtQhyojgO8HxC+FGaUsyYwlWOrCCK1lfFegG/cI2ZXxEl32ZydXINg2RqbZo8itB/ k1v4eb9Naih+tbErH9CLnqBDJFvTEMexjSxQgiDVxTNAku8x5VekbelUPdx030TPPuGo nxK3UtUNTpQjgjfX7FkDZDvo2gatb3IF3iJMhW9EuJYF/+ht3IFRmkAVnHDj8xY1EJVu D6iikcyNeQDPjirObNd9+31U3zaESovHtp9Su463keH73afcdVYvU1qcozQoYzBW5gJQ jN6evAD2IxfyOWlHD4QhpKPC6VsjYV3KKMQVMBPRKgzENfLVicYOiCkOA1c7erd9VE7D KgiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GgaA1p0fckS/xkVcv6xLVDzsEsvBNZIgKR6q+KUe7ZU=; b=LPvOPB3mMMSKrKCJUaBBQn86DXDX8R02pe5Ps6C2JemOipqeoIbqRYsD8SH1L76yFW rCDyVJaLDs/TaTx3keQ7+AgTiUe0TsNyCL8CN42Sf8v8H1VH0kaSRdac5+G/e+Q09MLB tiInJ/DUnKg6dgGzDXzgrD0GWBX82TuCihL2OK36tkOqqDxpvPWtfI13DXfhto6GHusT v+qx2kBdmt48wSS350sBBS6cE03X+X1aUxwO4tDy8DOq8EGMhiybaAJdxoCWqblfiOt4 VxsrBpvUcVJu52CWTpi8UihMXBkdy6hWzY8IucrwemhUqmIQmQr6U8UIM/04v+qzNESw az9w== X-Gm-Message-State: AMCzsaWK0JT3DFW+W4gYD2KoxgkLKXkP0ekGt7bZ0Z4mOBNX+XR11iDV lCu771ERJCDypfmApDiEGb+/fEC2uPzLheaRts0= X-Google-Smtp-Source: ABhQp+QWZHyIWWZlUOucntjQM4e64ona4FACTBNDHN2BKs8WxccLJjaFo00fOuiBpTiCl6F6GNd6isUfm0RphFnfX1M= X-Received: by 10.28.92.136 with SMTP id q130mr5387293wmb.35.1508091173541; Sun, 15 Oct 2017 11:12:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.173.129 with HTTP; Sun, 15 Oct 2017 11:12:52 -0700 (PDT) Received: by 10.223.173.129 with HTTP; Sun, 15 Oct 2017 11:12:52 -0700 (PDT) In-Reply-To: References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> From: =?UTF-8?Q?Eddy_Petri=C8=99or?= Date: Sun, 15 Oct 2017 21:12:52 +0300 Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: Warner Losh Cc: mmel@freebsd.org, freebsd-arm@freebsd.org, bob prohaska 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: Sun, 15 Oct 2017 18:12:55 -0000 Pe 14 oct. 2017 7:54 PM, "Warner Losh" a scris: On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" wr= ote: Pe 14 oct. 2017 7:28 AM, "Michal Meloun" a scris: On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!=3D uname -p >>> with >>> BUILD_ARCH!=3D echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darmv7 I have been trying recently to add support for cross building FreeBSD from Linux and concluded that MACHINE is the system on which the build is done. At the start of the build, yes. But we set it while doing the actual cross build to the target. You mean that although at the beginning of the cross build MACHINE* relates to the build system, later it relates to some other different meaning? I don't think I found BUILD* meaning yet. That's because they are internal and should never be messed with. They are a detail we don't commit to keeping. If they matter, we have done something wrong. What are the ones "set in stone"? The ones documented in the meanwhile? Unfortunately I concluded the FreeBSD build system would really benefit from a clean-up in terms of variables and documenting their use. May I suggest creating a wiki page documenting the usage a clean up can be done? We do document most of them in build man page. That's what should be updated. It spells this stuff out. Where can I find this in the source tree? Warner Eddy Petri=C8=99or From owner-freebsd-arm@freebsd.org Sun Oct 15 18:16:16 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 25146E483BB for ; Sun, 15 Oct 2017 18:16:16 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 A50A0820E7; Sun, 15 Oct 2017 18:16:15 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id i124so29603115wmf.3; Sun, 15 Oct 2017 11:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dPWru0A4v1gdrxKWLPxodx/ZaZQjbJPib214vNqO9eI=; b=eShDwxkY+T+SFv5x0NTEFcYf6hesBBI7Nlucpa6Zhde+lHs2Fu2jisd8Xlfg2o23zQ NBJcbImNh4k7H0ayr7Ju7cgRceTryxGVjIATGd7sYIveeRuab8Qlb/RvRZiBunVDrnWd zKi01t32PqQDQxWZlxRJBe0usIQx+FX+GegbQ2ddwJfjCjjv/0vN1VmqMjkN2n+oR/yd nDFBTzwYrzOBhloYaCdRws7HweZe0A8kenxvSU6EqVsVDwVN+8/fTm3rcQHTO1Jj1nnU nEDydo7eCuv36EP+frnSIQBuvsHNALa9qO0EDx7909DXck5i+k2/ay+1UqB6YyGbmuhC TROQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dPWru0A4v1gdrxKWLPxodx/ZaZQjbJPib214vNqO9eI=; b=lBO9IbMMAvtVpJM+9JdtTOdeA6RDCXaHLpHjBlSbZFjLB5S0oc2LfwCj1b6UhLcPtB ccaH+JigMW9M9Mn2MFDC19qf5ziJFuNp0yUKWsgdkb5XnBsrg4Q9SalcBQ3mwU+Exkzp qgAoKKDDMfEbrV1majuhIuCnJ7wxnY19X4ZxlUPSIeua7+FtYThGiTt4TsXGlKbPVFk/ lr3Mol9V3FQ6lrVAD6txHtPXXMOC3POo4SLRbKlZK0SauPfvRlKP/uJOK8Y4vkS426KS 7BW0EBWgvwMzX/Er4dKhiztR0cdaYuOgG2J4BAMXtohTZCkqvC3MWHmBH1+IDWT+PLoq xVXA== X-Gm-Message-State: AMCzsaWN2Ny+khXB8LFjWXwqZyjyXDgcCm/XHvXC8le1KvgWvsFafk2k aEWJ5c0suqkyKKqMZvCUEd+n/Hi+1M4V2xVrX5cnug4c X-Google-Smtp-Source: ABhQp+TlWbWMaVzpuXOnPbH1gu1vvhROSaZjsAMcxrXsGEJAH9jSMx9/uC0nVF3Ll70DtI+uFQ0QS7+7Ev3l/92ALHI= X-Received: by 10.28.131.13 with SMTP id f13mr6446384wmd.157.1508091374107; Sun, 15 Oct 2017 11:16:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.173.129 with HTTP; Sun, 15 Oct 2017 11:16:13 -0700 (PDT) Received: by 10.223.173.129 with HTTP; Sun, 15 Oct 2017 11:16:13 -0700 (PDT) In-Reply-To: References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> From: =?UTF-8?Q?Eddy_Petri=C8=99or?= Date: Sun, 15 Oct 2017 21:16:13 +0300 Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: Warner Losh Cc: mmel@freebsd.org, freebsd-arm@freebsd.org, bob prohaska 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: Sun, 15 Oct 2017 18:16:16 -0000 Pe 15 oct. 2017 9:12 PM, "Eddy Petri=C8=99or" a s= cris: Pe 14 oct. 2017 7:54 PM, "Warner Losh" a scris: On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" wr= ote: Pe 14 oct. 2017 7:28 AM, "Michal Meloun" a scris: On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!=3D uname -p >>> with >>> BUILD_ARCH!=3D echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darmv7 I have been trying recently to add support for cross building FreeBSD from Linux and concluded that MACHINE is the system on which the build is done. At the start of the build, yes. But we set it while doing the actual cross build to the target. You mean that although at the beginning of the cross build MACHINE* relates to the build system, later it relates to some other different meaning? I don't think I found BUILD* meaning yet. That's because they are internal and should never be messed with. They are a detail we don't commit to keeping. If they matter, we have done something wrong. What are the ones "set in stone"? The ones documented in the meanwhile? *the makefile Unfortunately I concluded the FreeBSD build system would really benefit from a clean-up in terms of variables and documenting their use. May I suggest creating a wiki page documenting the usage a clean up can be done? We do document most of them in build man page. That's what should be updated. It spells this stuff out. Where can I find this in the source tree? Warner Eddy Petri=C8=99or From owner-freebsd-arm@freebsd.org Sun Oct 15 18:55:35 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 33A44E48CAD for ; Sun, 15 Oct 2017 18:55:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 EE49C82FCC for ; Sun, 15 Oct 2017 18:55:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id 189so13831152iow.10 for ; Sun, 15 Oct 2017 11:55:34 -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=dQnRrUDhKooSCbA4P42C1vT7zh3L3BUDW6s2GGOHck4=; b=NK6QsWbY66jkx2eAkoZdVJAlAcb7MgbKakMljakG6vw4tWHd/1jcQGTtRf9UGha6Sg m5bD3msjB2t1XBhmIv8UHYhDFNGnghmfYodu6WYfB48wmK1ZTsnsKMiQeFCbEt3z/+I+ 0UioHWkd1hZRDDg0msSfa2TgmPbfHCXNFpmkp+MNr+vtjLStdgVjpeIeE2P4VXARLgV3 gP1L5JYO/8CPvd5deT4NPxLbkh1j2ptENhHtn0pbf0q7DzpbfZP2qu5fwHGuNNH1g7R3 kQTar9ge2oNqoNLRVlX/eT8IbrSyfEQPmq9BeivyYRTk5iJrVvLlmH7mtQCoj+1HnQCD UR+Q== 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=dQnRrUDhKooSCbA4P42C1vT7zh3L3BUDW6s2GGOHck4=; b=k+OQq67uvkjM7DYa5iMqn/WCbs3D0GR/16rni2HAZwOOq3wHaMdpTqnCWq1v4Kn+KZ kckISrA64y4A3Bo2xB8PfbIyrRGCQOCGpSeTZwppLOWE3eDg1hFqRMUvTkXkcoJICsDo Kb9RnhE1M6wbXOJOzIoXUngKoAVXNY8Hs03lQwjz7cXt7QOWZFX2wAzScssMURI/bQ6i yXYOYCbh8VvHgtklWhrDjlwyRLbymv86rq7DjXj97aEWvoYCTd9rlT8xu2fCmCFS9XV5 9kqUOtMtPfwBlaoxRMrBiiaq8OXOYhRYa7kBTpixH8sKqxEMSEGCMfOHHOt+BAAFD2dr olTg== X-Gm-Message-State: AMCzsaWtg6QgOPA3rs19cpBWHkUE3yrU0+lJ6RQ4s1wWEPx2cdpIBARr 9FPfCS/BqkBkbtb8LpslPnKKG/1bPpG76gg5wAXy5g== X-Google-Smtp-Source: AOwi7QA/94n5CqvqvNUDrSTi22EeWPKkzBWGm6RGmm+o0EvUkqvKZs1IWj88tN6ZkvKDK8AfJKs0ZvawZTGCeFeg0Cs= X-Received: by 10.107.114.5 with SMTP id n5mr10495657ioc.291.1508093734091; Sun, 15 Oct 2017 11:55:34 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Sun, 15 Oct 2017 11:55:33 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:a0b5:c8ee:5cc8:3aa5] In-Reply-To: References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> From: Warner Losh Date: Sun, 15 Oct 2017 12:55:33 -0600 X-Google-Sender-Auth: qlu6zcPstqzvKAqY71YH-I5DqvY Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: =?UTF-8?Q?Eddy_Petri=C8=99or?= Cc: Michal Meloun , "freebsd-arm@freebsd.org" , bob prohaska 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: Sun, 15 Oct 2017 18:55:35 -0000 On Sun, Oct 15, 2017 at 12:12 PM, Eddy Petri=C8=99or wrote: > > Pe 14 oct. 2017 7:54 PM, "Warner Losh" a scris: > > > > On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" = wrote: > > Pe 14 oct. 2017 7:28 AM, "Michal Meloun" a scris= : > > > > On 14.10.2017 4:11, bob prohaska wrote: > > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: > >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: > >> > >>> Seems it would have been better to replace > >>> BUILD_ARCH!=3D uname -p > >>> with > >>> BUILD_ARCH!=3D echo armv7 > >>> for present purposes. > >> > >> Are you starting under armv6 ? armv7 ? > > I'm afraid it's a mix, due to some untimely foot-shooting. > > > > Uname - p reports armv7, but clang -v reports > > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > LLVM 4.0.0) > > Target: armv6-unknown-freebsd12.0-gnueabihf > > Thread model: posix > > InstalledDir: /usr/bin > > > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > > snapshot is released, then start over if necessary. > > > > Thanks for reading! > > > > bob prohaska > > > Bob, > can you please try this? > setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darm= v7 > > > I have been trying recently to add support for cross building FreeBSD fro= m > Linux and concluded that MACHINE is the system on which the build is done= . > > > At the start of the build, yes. But we set it while doing the actual cros= s > build to the target. > > > You mean that although at the beginning of the cross build MACHINE* > relates to the build system, later it relates to some other different > meaning? > > I don't think I found BUILD* meaning yet. > > > > That's because they are internal and should never be messed with. They ar= e > a detail we don't commit to keeping. If they matter, we have done > something wrong. > > > What are the ones "set in stone"? The ones documented in the meanwhile? > > Unfortunately I concluded the FreeBSD build system would really benefit > from a clean-up in terms of variables and documenting their use. May I > suggest creating a wiki page documenting the usage a clean up can be done= ? > > > We do document most of them in build man page. That's what should be > updated. It spells this stuff out. > > > Where can I find this in the source tree? > > % man build or ./share/man/man7/build.7 Warner From owner-freebsd-arm@freebsd.org Sun Oct 15 19:09:54 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 B588AE48FD2; Sun, 15 Oct 2017 19:09:54 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32B1283404; Sun, 15 Oct 2017 19:09:53 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.228.157.238]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MAyVY-1dw53F1iZ2-009xOG; Sun, 15 Oct 2017 21:09:45 +0200 Date: Sun, 15 Oct 2017 21:09:35 +0200 From: "O. Hartmann" Cc: freebsd-arm@FreeBSD.org, FreeBSD Questions Subject: Re: NanoBSD: Current/NANO_ARCH=aarch64: chroot: : No such file or directory Message-ID: <20171015210935.5a50a85a@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20171012153922.6e747356@hermann> References: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> <1507762426.8386.24.camel@freebsd.org> <20171012153922.6e747356@hermann> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/VEohY/ZPeRQcvsDZPOmJLyo"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:a3mv5UZndTCntjdAgVOfgfRM4QR/tZktCtBsXP3wv4+o4jW4nqz IAaFKXNGRYc9EQNbTR597EdVnT2UsogU5Urdemz6e23fa/LFSN0u8B6NA4HdsG+q/qkbZ0P WIVDHfHNMaFbIy/UwOZDe1+j/f8xVeGe9u8ABZbf8o/CLiWOP+CddmKFog/yZYsvwKy7Yej zHoHqhdBMTFn3KsUq4buw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ZoWINQc4wms=:1oGfow6QDY9593w5d+/Y/0 k7jUUpnMVwyW0QAR2+vJGWPb3IWA92Py2QBzCyd82j1d91WaIOZDD00MY5UsXufd7CXjYROs5 Wen4x9CwGLAR/5V9MEII8/JewEPWWSAD5Pakse4BPr+NaI0+NA2vPef0dTsdciTE59ZIp/YPJ 34ylG5z+zLQSLYsGaF3sOe0kufLXwvS/SRj0QLNpPz9gDe06ObGwa8Dk0ncrOaxacRIt1YDVQ /pHxAweN/58HsAUGqBAn4ezsXqhqtRE1CFNYfPOCzJG8/7yLHbbYxOafWc0bKltAKF+rw1GjZ zeSZD7a+YfMspB8TIZY6hvNJEHMA3/DNYjDuMwNtYRqnxHJjPgQvRbPgSmY/ch3igqk0Gcqh2 bhCD9glhuCng4ZE2QuDjrEx2cCVr5JKAx9OoCeE3Cg+adJiE4w01OgIdvCwZqs5au1P1T4G8S 1cVTHA6Mc0DyEXVnLqa5eYCAr56iK/1VBPgeO+W8fa9zvVyuVsev3boTgA2ZXIi/GxktZQk40 rptluq3CHQAMEF/PkAe1s6zx/eLFCsgZtpS0MdDZo/INIQQFdX9T5Zxp2E682UawLtMkN0YG3 BmTfzpgSNokPlKbgyqs2K+DLy5aZjUP1l4OLgyFL5kDlQL1WEIekD3rt7icdEBA2ij9DjLmL9 VSqIjtCJcSUPECWzc7rHOv4a8NwWro6YmOW29sIiM5dy9IkFi42f9PU1Dd40yTuwjdMK6zTfO e/v7IB6ec0dhiwvtdNwCCCNupsuMiNF0W919emq4zWHwe+LgyADRFDxBuq/up5BMKJODryg8m Tn1RzDdxdX+icnHSxTvIcrkE+9wIiIAY4PQjrfRkr0cxuBeQYuzLNewEdaeTv0V4okf+Agwfj YfcbmBKo3nIhO11AzXK9KMzwMBSNk5p1dA6VfWlto= 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: Sun, 15 Oct 2017 19:09:54 -0000 --Sig_/VEohY/ZPeRQcvsDZPOmJLyo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am Thu, 12 Oct 2017 15:39:26 +0200 "Hartmann, O." schrieb: > On Wed, 11 Oct 2017 16:53:46 -0600 > Ian Lepore wrote: >=20 > > On Wed, 2017-10-11 at 20:47 +0200, O. Hartmann wrote: =20 > > > Trying to install a successfully cross compiled FreeBSD > > > (TARGET=3Darm64) as NanoBSD. NanoBSD is configure using > > > NANO_ARCH=3D"aarch64". > > >=20 > > > Port emulators/qemu-user-static is installed and loaded: > > >=20 > > > =A08=A0=A0=A0=A01 0xffffffff8243f000 1564=A0=A0=A0=A0=A0imgact_binmis= c.ko > > >=20 > > > When installing NanoBSD's world and then running mtree, the nanobsd > > > script runs into this error: > > >=20 > > > /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local > > > 283 blocks > > > + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ > > > -f /home/user/Projects/router/nanobsd/mtree/Files.mtree > > > ] > > > + CR 'mtree -eiU -p /' > > > + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc > > > 'mtree -eiU -p /' chroot: : No such file or directory =20 >=20 > Oops, I confused the output. >=20 > The correct one is: >=20 > [ from _.cust.cust_install_files ] >=20 > ... > + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree > -eiU -p /' chroot: /bin/sh: No such file or directory >=20 > The empty '' is due to my (hopeless helpless) attempt to fit-in another > variable which was set to an empty string. >=20 > The error looks to me as chroot does't find the proper shell, /bin/sh, > but it has been properly installed: >=20 > # file _.w/bin/sh > _.w/bin/sh: ELF 64-bit LSB executable, ARM aarch64, version 1 > (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for > FreeBSD 12.0 (1200051), FreeBSD-style, stripped >=20 > # ll _.w/bin/sh > 839832 -r-xr-xr-x 1 root wheel uarch 261K 12 Okt. 15:32 _.w/bin/sh >=20 > NanoBSD works on the native host when building on host arch amd64 for > host arch amd64 and I guess it is due to the properly installed OS of > the host. >=20 > I do not get the problem here. qemu_user_static should catch up with > the alien binary here - I suppose it does. The absolute path should > ensure the use of the right binary ... >=20 > Regards, >=20 > Oliver >=20 > > > =20 > >=20 > > I'm not sure how or why it's happening (I've never used nanobsd), but > > the complaint is about those empty quotes ('') between the pathname > > and the /bin/sh in the chroot command. =A0It's trying to run a program > > named '' and chroot is complaining that it can't find anything named > > that. > >=20 > > -- Ian > > =20 > > > Is there anything I miss here with the QEMU emulator catching up? > > >=20 > > > Thanks in advance, > > >=20 > > > Oliver > > > =20 >=20 I didn't find a solution to this problem, it might be that someone has alre= ady have such a problem solved, so I'm sending CC'ed also to the list "questions". The background is above described. Running most recent qemu-user-static (qemu-user-static-2.9.94.g20171011), l= oaded and running a kernel module, chrooting into a cross-compiled aarch64 installati= on of recent 12-CURRENT (r324621) fails with error (from NanoBSD): [...] chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree -eiU -p /' chroot: /bin/sh: No such file or directory There is no further output so I fly blind. As mentioned above, /bin/sh is i= nstalled and present in the chrooted target folder and file states, that it has been co= mpiled for aarch64. I tried manually the very same command - amongst other attempts to chroot a= nd execute a command - but always the same: I get the error shown above, no such file or= directory. Do I miss something here? Do I have to install some crosse development tool= s/libs into the chrooted target first, so /bin/sh can be emulated correctly? I'm quite new to cross compiling. But at this point with this thin, faintin= g amount of information why it fails, I can't even start searching ... Hopefully someone can shed some light on this. Thanks in advance, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 BDS= G). --Sig_/VEohY/ZPeRQcvsDZPOmJLyo Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWeOybwAKCRDS528fyFhY lFHmAf98Ypw4dHXVM+7ALrH9Ecinqdxt6qNawMKwuL1hVQda5DLX7rCIVNkMhLSI lm1X78roO+KtV1Uc87Jl/Ib0GJ9GAf4jjCVjW+/WItAH68l/TQvng/NeOmyC3N4/ LodI5HkspYNEr0JOYGc0I7j3KWZ2kR03Z8XAEAgj/fxaMJAXBPMV =e8TZ -----END PGP SIGNATURE----- --Sig_/VEohY/ZPeRQcvsDZPOmJLyo-- From owner-freebsd-arm@freebsd.org Mon Oct 16 03:57:15 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 C1FD5E2CC2D for ; Mon, 16 Oct 2017 03:57:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 039AB6A9D8 for ; Mon, 16 Oct 2017 03:57:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9G3vH5b092730 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 15 Oct 2017 20:57:18 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9G3vHYL092729; Sun, 15 Oct 2017 20:57:17 -0700 (PDT) (envelope-from fbsd) Date: Sun, 15 Oct 2017 20:57:17 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171016035716.GA92612@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171013175943.GA74121@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) 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, 16 Oct 2017 03:57:15 -0000 With the kernel at r324562, /usr/src at r324599, /usr/src/Makefile.inc1 showing #.if make(buildworld) #BUILD_ARCH!= uname -p BUILD_ARCH!= echo armv7 #.if ${MACHINE_ARCH} != ${BUILD_ARCH} #.error To cross-build, set TARGET_ARCH. #.endif #.endif and /etc/make.conf containing KERNCONF=RPI2 TARGET=arm TARGET_ARCH=armv7 DESTDIR=/ make buildworld ran until it crashed with a PT2MAP panic, as it has done many times before. The log file reached 26 MB, it probably had to go a little over 30 MB to finish. The console, top and logfile are at http://www.zefox.net/~fbsd/rpi2/crashes/crash_10_15_17/ The machine has been rebooted to a v6 kernel which has built world in the past, r322520, though it too has crashed with PT2MAP errors at least once. /usr/src/Makefile.inc1 has been restored and buildworld restarted with make -j4 buildworld TARGET_ARCH=armv7 > buildworld.log & There are no immediate errors, I'll let the build run unless someone suggests a reason to try something else. The reply threads have become somewhat tangled, I'll trim here for sake of brevity. Thanks for reading!! bob prohaska > > bob prohaska > > On Thu, Oct 12, 2017 at 07:06:04PM -0700, bob prohaska wrote: > > It's starting to look as if the trouble might have little or nothing > > to do with the armv6-armv7 transition and instead has some other cause. > > > > At this point /etc/make.conf contains > > KERNCONF=RPI2 > > TARGET=arm > > TARGET_ARCH=armv7 > > DESTDIR=/ > > > > Buildkernel works, installkernel demanded a DESTDIR and worked once it > > was added, so /etc/make.conf is being read and acted upon. > > > > If make buildworld is invoked, using the make.conf file above, make reports > > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. > > *** [buildworld] Error code 1 > > > > I had to reconstruct all of /usr after mistakenly deleting it during an > > attempted housecleaning. The restored /usr seems to boot normally and > > builds kernels just fine, but does not allow su to root, so permissions > > (or something) are not entirely correct. > > > > Might this be related to the failure to recognize or act upon the > > TARGET_ARCH=armv7 setting? /usr/src is at 324562, along with the > > kernel. Userland dates from late June. > > > > Thanks for reading, and any ideas. > > > > bob prohaska > > > > On Tue, Oct 10, 2017 at 08:00:21PM -0700, bob prohaska wrote: > > > On Tue, Oct 10, 2017 at 08:41:17PM -0600, Warner Losh wrote: > > > > On Tue, Oct 10, 2017 at 8:39 PM, Warner Losh wrote: > > > > > > > > > > > > > > > > > > > On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > > > > > > > > > >> On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > > > > >> > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > > > >> > > On an RPI2 model B, invoking? > > > > >> > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > > > >> > > > > > >> > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > > > > >> > TARGET_ARCH when installing as well. > > > > >> > > > > >> Tried it, like so: > > > > >> root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > > > > > >> buildworld.log & [1] 1006 > > > > >> root@www:/usr/src # 1 error > > > > >> > > > > >> [1] Exit 2 make -j4 buildworld > > > > >> TARGET_ARCH=armv7 > buildworld.log > > > > >> root@www:/usr/src # more *.log > > > > >> --- buildworld --- > > > > >> make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > > > > >> TARGET_ARCH. > > > > >> *** [buildworld] Error code 1 > > > > >> > > > > >> make: stopped in /usr/src > > > > >> > > > > >> I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various > > > > >> iterations. Should the variables be set somewhere else, in a config file? > > > > >> > > > > >> At this point the kernel is at r324499, along with the sources. Userland > > > > >> dates from late June (operator error). Kernels build, but could that make > > > > >> the trouble I'm seeing? Clang -v reports > > > > >> > > > > >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > > > > >> LLVM 4.0.0) > > > > >> Target: armv6-unknown-freebsd12.0-gnueabihf > > > > >> Thread model: posix > > > > >> InstalledDir: /usr/bin > > > > >> > > > > >> Thanks again! > > > > > > > > > > > > > > > uname -a says what? > > > > > > > > > > > > root@www:/usr/src # > > > root@www:/usr/src # uname -a > > > FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r324499: Tue Oct 10 18:06:39 PDT 2017 root@www.zefox.com:/usr/obj/usr/src/sys/RPI2 arm > > > > > > > What happens if you do a build with TARGET_ARCH=armv7? > > > > > > > > > > root@www:/usr/src # make TARGET_ARCH=armv7 buildworld > buildworld.log > > > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. > > > root@www:/usr/src # > > > > > > FWIW, /etc/make.conf does not exist. Seemingly the variable isn't recognized. > > > Maybe a config error someplace? > > > > > > Thanks again, > > > > > > bob prohaska > > > From owner-freebsd-arm@freebsd.org Mon Oct 16 05:51:41 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 161D7E2F173 for ; Mon, 16 Oct 2017 05:51:41 +0000 (UTC) (envelope-from per@hedeland.org) Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FAC46DFFC for ; Mon, 16 Oct 2017 05:51:39 +0000 (UTC) (envelope-from per@hedeland.org) X-MHO-User: e943f19f-b235-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 81.228.155.109 X-Mail-Handler: DuoCircle Outbound SMTP Received: from hedeland.org (unknown [81.228.155.109]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id e943f19f-b235-11e7-a893-25625093991c; Mon, 16 Oct 2017 05:50:27 +0000 (UTC) Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id v9G5oNSn099379 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 16 Oct 2017 07:50:24 +0200 (CEST) (envelope-from per@hedeland.org) Subject: Re: NanoBSD: Current/NANO_ARCH=aarch64: chroot: : No such file or directory To: "O. Hartmann" Cc: freebsd-arm@FreeBSD.org, FreeBSD Questions References: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> <1507762426.8386.24.camel@freebsd.org> <20171012153922.6e747356@hermann> <20171015210935.5a50a85a@thor.intern.walstatt.dynvpn.de> From: Per Hedeland Message-ID: <7dde9642-c45b-ac92-b130-05cbd4bdeed4@hedeland.org> Date: Mon, 16 Oct 2017 07:50:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171015210935.5a50a85a@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 16 Oct 2017 05:51:41 -0000 On 2017-10-15 21:09, O. Hartmann wrote: > Am Thu, 12 Oct 2017 15:39:26 +0200 > "Hartmann, O." schrieb: > > > >> On Wed, 11 Oct 2017 16:53:46 -0600 >> Ian Lepore wrote: >> >>> On Wed, 2017-10-11 at 20:47 +0200, O. Hartmann wrote: >>>> Trying to install a successfully cross compiled FreeBSD >>>> (TARGET=arm64) as NanoBSD. NanoBSD is configure using >>>> NANO_ARCH="aarch64". >>>> >>>> Port emulators/qemu-user-static is installed and loaded: >>>> >>>> 8 1 0xffffffff8243f000 1564 imgact_binmisc.ko >>>> >>>> When installing NanoBSD's world and then running mtree, the nanobsd >>>> script runs into this error: >>>> >>>> /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local >>>> 283 blocks >>>> + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ >>>> -f /home/user/Projects/router/nanobsd/mtree/Files.mtree >>>> ] >>>> + CR 'mtree -eiU -p /' >>>> + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc >>>> 'mtree -eiU -p /' chroot: : No such file or directory >> >> Oops, I confused the output. >> >> The correct one is: >> >> [ from _.cust.cust_install_files ] >> >> ... >> + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree >> -eiU -p /' chroot: /bin/sh: No such file or directory >> >> The empty '' is due to my (hopeless helpless) attempt to fit-in another >> variable which was set to an empty string. >> >> The error looks to me as chroot does't find the proper shell, /bin/sh, >> but it has been properly installed: >> >> # file _.w/bin/sh >> _.w/bin/sh: ELF 64-bit LSB executable, ARM aarch64, version 1 >> (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for >> FreeBSD 12.0 (1200051), FreeBSD-style, stripped >> >> # ll _.w/bin/sh >> 839832 -r-xr-xr-x 1 root wheel uarch 261K 12 Okt. 15:32 _.w/bin/sh >> >> NanoBSD works on the native host when building on host arch amd64 for >> host arch amd64 and I guess it is due to the properly installed OS of >> the host. >> >> I do not get the problem here. qemu_user_static should catch up with >> the alien binary here - I suppose it does. The absolute path should >> ensure the use of the right binary ... >> >> Regards, >> >> Oliver >> >>>> >>> >>> I'm not sure how or why it's happening (I've never used nanobsd), but >>> the complaint is about those empty quotes ('') between the pathname >>> and the /bin/sh in the chroot command. It's trying to run a program >>> named '' and chroot is complaining that it can't find anything named >>> that. >>> >>> -- Ian >>> >>>> Is there anything I miss here with the QEMU emulator catching up? >>>> >>>> Thanks in advance, >>>> >>>> Oliver >>>> >> > > I didn't find a solution to this problem, it might be that someone has already have such > a problem solved, so I'm sending CC'ed also to the list "questions". > > The background is above described. > > Running most recent qemu-user-static (qemu-user-static-2.9.94.g20171011), loaded and > running a kernel module, chrooting into a cross-compiled aarch64 installation of recent > 12-CURRENT (r324621) fails with error (from NanoBSD): > > [...] > chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree -eiU -p /' > chroot: /bin/sh: No such file or directory I have no idea if this is your problem, nor actually what you're trying to do - I just want to point out that you can get this ENOENT error for an executable not only when the executable doesn't exist, but also when the loader a.k.a. "interpreter" that the executable wants doesn't exist. I.e. check whether you have /libexec/ld-elf.so.1 in the chroot tree. --Per Hedeland > There is no further output so I fly blind. As mentioned above, /bin/sh is installed and > present in the chrooted target folder and file states, that it has been compiled for > aarch64. > > I tried manually the very same command - amongst other attempts to chroot and execute a > command - but always the same: I get the error shown above, no such file or directory. > > Do I miss something here? Do I have to install some crosse development tools/libs into > the chrooted target first, so /bin/sh can be emulated correctly? > > I'm quite new to cross compiling. But at this point with this thin, fainting amount of > information why it fails, I can't even start searching ... > > Hopefully someone can shed some light on this. > > Thanks in advance, > > oh > From owner-freebsd-arm@freebsd.org Mon Oct 16 12:23:04 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 11EC2E39648 for ; Mon, 16 Oct 2017 12:23:04 +0000 (UTC) (envelope-from hrabanek@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 982B87E909 for ; Mon, 16 Oct 2017 12:23:03 +0000 (UTC) (envelope-from hrabanek@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id b189so2614350wmd.4 for ; Mon, 16 Oct 2017 05:23:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=HbMFNdIe2WV4TlaJtNv3gwDPHwuSgZmlIVesHjgnTQU=; b=pjChFAODKz3r1M+VAxPmZFlo6NfDE2KgX11ea2LS2iTISIiOgGajgOQWH+PkGaC/Uu wR8bVNQsgfos+R4b4gdHGpfIHy8Pe4FrvxKOIjlhhFRjegbQP2vazwFHW68OqHFgIWcT qGqFlybbhj6aVluWy7HCSkY3RGxD+biL9cjAb3LERHWL38rhBOfIOWHjCow2cCDvid9p URvo0j1WUNTrthHgeHdKlx+q8HcgYGFeM/1nFB4QUfCAbd0AJ/Mu/O0KtKpeX0Gz463Q KmzcBuhiay0QPDFEtkWfkIg+K4SM2uSiotZ5liqgeaD2ufn/3beaXH5+e0ULTHpcm5mk h2Gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=HbMFNdIe2WV4TlaJtNv3gwDPHwuSgZmlIVesHjgnTQU=; b=j12C8Pj/f/rXIwJAUaqKmiYON6R/5Kl/LJeiBzMM2t+mb5R1IFR376OYpZlpBsPNRh bUAS8qKLOWxk0rneCBnx48hyYpvGOIxPmAYMnKWyQ6oplskplkGymBh+b2SnWuWpfj25 OSpZLE9RE4Dsgye+pzMtHW8i0xdqdzszE1YTXWlaeRVE2BqBbfPxENlUnC8/XpkmT5fZ VeB9d+Hx1RvwtUy0MX4jUjhGxBmVqZh0tJmMYdhpBbAjxzH/cGCm+cIvu2v5qSA+oR8g 0xpjYG17Ixswt5xWCyXeoj53NNIdKxZ2y1c8RVV+ccghtEo3Cx4s1YycGPf5j+l61q5D +VWQ== X-Gm-Message-State: AMCzsaWWNuQrSfACBDzVdaR1CGszAy9v59V4MyD63FTYs3OdtaxWTBr6 X7AkvjBH/EbOd86yylvvbi+H8+J80dTxEnk8xI6sTA== X-Google-Smtp-Source: AOwi7QA2x8pFV2nxeCl09odp6VlkQT6SXIqAOV4UWruj1W+nVBWRl7TRXh0XHZRqpZWmdraM7ontnR5K6Y8h+pEdDQA= X-Received: by 10.80.135.9 with SMTP id i9mr12863300edb.31.1508156582077; Mon, 16 Oct 2017 05:23:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.183.98 with HTTP; Mon, 16 Oct 2017 05:23:01 -0700 (PDT) In-Reply-To: <20171007185116.6aa97faf3511ebf90a06301d@bidouilliste.com> References: <20170921082259.aa46e554e653ce7bf2d403b2@bidouilliste.com> <20171003133901.1de20ce9637720671eee3d33@bidouilliste.com> <20171007185116.6aa97faf3511ebf90a06301d@bidouilliste.com> From: Michael Hrabanek Date: Mon, 16 Oct 2017 14:23:01 +0200 Message-ID: Subject: Re: Allwinner H3 (NanoPi Neo): Getting PORTL (on /dev/gpioc1) to work To: Emmanuel Vadot , 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, 16 Oct 2017 12:23:04 -0000 I can confirm the gpio driver now works flawlessly, thank you very much! Michael On Sat, Oct 7, 2017 at 6:51 PM, Emmanuel Vadot wrote: > > Hello, > > On Tue, 3 Oct 2017 13:39:01 +0200 > Emmanuel Vadot wrote: > > > On Tue, 3 Oct 2017 13:27:47 +0200 > > Michael Hrabanek wrote: > > > > > Hello, > > > any updates? If you'll need any testing done I'd be happy to help > > > > > > Cheers, > > > Michael > > > > I've fixed our gpio driver to not attach if we cannot enable one of > > the needed clocks. > > Now I need to code the clock driver for H3, it seems that there is no > > docs so it will take some time. > > I commited the driver in r324383, let me know if you have any problems. > > Cheers, > > -- > Emmanuel Vadot > From owner-freebsd-arm@freebsd.org Mon Oct 16 19:27: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 963D4E42D74 for ; Mon, 16 Oct 2017 19:27:06 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E1E5769847 for ; Mon, 16 Oct 2017 19:27:05 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 1c31f665; Mon, 16 Oct 2017 21:27:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=iHoWHj0vRD9RmNkUm+pIArmCpGY=; b=BZGqplaMEInhnM2mzPRwSYintSlk Q5cUvUmUI5OtDEBuKd6ZUy6QrncKqqMpIM55pkIKEet8BsIz/4LJ3R5daegQP3Lo r940EcdvSUlL9917pfOUGvtFSKRCk53/VDXcfNUxIE/I2C1FpvQZwcFKCgebjszt 7GPyL8+IXoPqNMc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=sgCGUkiQ5kPFIs1S6zZ6bJaQ1CBrEApt42FVMpBIdRDOd1TV5an03K80 fINlk0AGFkunHbXuPUzVIEQGUqQFHk6+qWYh0lEX7jUD/K5IPFQaa+wlRun/ylP1 2ICOPdqfow96T4iOtac1M4IaT4B53xIbXDC1J/usUjaXCOdlzk8= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 2514231a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 16 Oct 2017 21:27:03 +0200 (CEST) Date: Mon, 16 Oct 2017 21:27:02 +0200 From: Emmanuel Vadot To: Michael Hrabanek Cc: freebsd-arm@freebsd.org Subject: Re: Allwinner H3 (NanoPi Neo): Getting PORTL (on /dev/gpioc1) to work Message-Id: <20171016212702.f77d4c421bd13ea561634f8f@bidouilliste.com> In-Reply-To: References: <20170921082259.aa46e554e653ce7bf2d403b2@bidouilliste.com> <20171003133901.1de20ce9637720671eee3d33@bidouilliste.com> <20171007185116.6aa97faf3511ebf90a06301d@bidouilliste.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 16 Oct 2017 19:27:06 -0000 On Mon, 16 Oct 2017 14:23:01 +0200 Michael Hrabanek wrote: > I can confirm the gpio driver now works flawlessly, > thank you very much! > > Michael Thank you for the confirmation, always good to see such email :) > On Sat, Oct 7, 2017 at 6:51 PM, Emmanuel Vadot > wrote: > > > > > Hello, > > > > On Tue, 3 Oct 2017 13:39:01 +0200 > > Emmanuel Vadot wrote: > > > > > On Tue, 3 Oct 2017 13:27:47 +0200 > > > Michael Hrabanek wrote: > > > > > > > Hello, > > > > any updates? If you'll need any testing done I'd be happy to help > > > > > > > > Cheers, > > > > Michael > > > > > > I've fixed our gpio driver to not attach if we cannot enable one of > > > the needed clocks. > > > Now I need to code the clock driver for H3, it seems that there is no > > > docs so it will take some time. > > > > I commited the driver in r324383, let me know if you have any problems. > > > > Cheers, > > > > -- > > Emmanuel Vadot > > -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 16 19:54:57 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 6B529E43806 for ; Mon, 16 Oct 2017 19:54:57 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 092356A824 for ; Mon, 16 Oct 2017 19:54:56 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1508183693; s=domk; d=obsigna.com; h=To:Date:Subject:Mime-Version:Content-Type:From; bh=OxL4/9yyS6PgFF7pum1AoyqsXkruaxO5wgZvmz6s3xY=; b=jYY8PtJlDgyHffxazBHmCwknYnBrnotmtIZP/YCc3CxKWKoAb+ssUGNnLiGkVi+6nn 3flpToKNn/w+ONdxhzN10ExhTi2cWrRbupw7LXFHeOChAICUHlJLacLja1UAjyBu9gRF sgCscI3nuj0xlPGUvIjlCjusdTCmSKfNqvu0o= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhS0fwIz0hhE+lDkJmR/zkZ585QgNmUK62cRj/0nG X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (bb02b41e.virtua.com.br [187.2.180.30]) by smtp.strato.de (RZmta 42.6 DYNA|AUTH) with ESMTPSA id 4014e1t9GJsr58K (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Mon, 16 Oct 2017 21:54:53 +0200 (CEST) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id BAE761350F919 for ; Mon, 16 Oct 2017 17:54:49 -0200 (BRST) From: "Dr. Rolf Jansen" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FreeBSD 12-CURRENT-ARMv7 and the BeagleBone Black Message-Id: <390DFE72-FE55-405E-831F-7892EF039B52@obsigna.com> Date: Mon, 16 Oct 2017 17:54:48 -0200 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=us-ascii 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, 16 Oct 2017 19:54:57 -0000 Hello, I saw the first ARMv7 snapshot images (Pandaboard and Hummingboard) = arrived on the FreeBSD ftp server. AFAIK, the BBB is ARMv7 as well. I am going to setup a new system on a = BeagleBone Black, and I am wondering whether I want to stay with the = 12-CURRENT-ARMv6 like my other setups, or whether it would be a good = idea to install a 12-CURRENT-ARMv7. Questions: would the ARMv7 flavor of FreeBSD run on a BeagleBone Black? if yes, will snapshots of 12-CURRENT-ARMv7 be available for the = BeagleBone in a foreseeable future? can I expect any advantages (disadvantages) from the ARMv7 architecture = compared to the ARMv6 one? if there are no plans for BBB ARMv7 snapshots, would it be worth the = efforts to build a ARMv7 BBB system from sources? Please don't take this as a demand, I am only curious. Many thanks for any advise. Best regards Rolf From owner-freebsd-arm@freebsd.org Mon Oct 16 20:01:40 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 DF51BE43BB1 for ; Mon, 16 Oct 2017 20:01:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 41F0D6ABB6 for ; Mon, 16 Oct 2017 20:01:39 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id ea067871; Mon, 16 Oct 2017 22:01:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=0aZN8e/oY61fPobbUsdML9Y3YDc=; b=WeXDyGZqIlDLzZWx8jIOc5mwdt0u /ju63qz3kXgntZFfK9eUMO3bfX8Pgg8m6uFZ7vBwaTFiN7Podr163DH/XEiEENPE hM13VJSdXyZt6Dd+ksv6Wjp6HnKDtCPjj1RohulYWoCj0Xl3gaZZ3bEdz/YVaTUi VgD6pUvYBHvmRRU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=Hz0RZ4rCfWw5uVC8yKh0hlgI1HMpemX4OhXJr8q/nUcRfvwjn420nkpN G0XoO5hllG4s723qjqfw2WHJxi4F45QWMfIwNPm0/P//4O7S9JmVf0M247zdDmWg FYzGR+vzxzQzRJoqErlXFSaierJTPnfpdTnqZL+MgcIHtFkimzI= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 01d97e75 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 16 Oct 2017 22:01:37 +0200 (CEST) Date: Mon, 16 Oct 2017 22:01:37 +0200 From: Emmanuel Vadot To: "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD 12-CURRENT-ARMv7 and the BeagleBone Black Message-Id: <20171016220137.7d9257804b39cb9f5a6587aa@bidouilliste.com> In-Reply-To: <390DFE72-FE55-405E-831F-7892EF039B52@obsigna.com> References: <390DFE72-FE55-405E-831F-7892EF039B52@obsigna.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 16 Oct 2017 20:01:41 -0000 On Mon, 16 Oct 2017 17:54:48 -0200 "Dr. Rolf Jansen" wrote: > Hello, Hi, > I saw the first ARMv7 snapshot images (Pandaboard and Hummingboard) arrived on the FreeBSD ftp server. > > AFAIK, the BBB is ARMv7 as well. I am going to setup a new system on a BeagleBone Black, and I am wondering whether I want to stay with the 12-CURRENT-ARMv6 like my other setups, or whether it would be a good idea to install a 12-CURRENT-ARMv7. > > Questions: > would the ARMv7 flavor of FreeBSD run on a BeagleBone Black? Yes, Glen (gjb@) already made the switch for the releases snapshot for that. > if yes, will snapshots of 12-CURRENT-ARMv7 be available for the BeagleBone in a foreseeable future? See above. > can I expect any advantages (disadvantages) from the ARMv7 architecture compared to the ARMv6 one? Maybe not right now but with packages/ports stuff dealt by Mark Linimon, mmel@ and miki yes probably. > if there are no plans for BBB ARMv7 snapshots, would it be worth the efforts to build a ARMv7 BBB system from sources? > Please don't take this as a demand, I am only curious. > > Many thanks for any advise. > > Best regards > > Rolf > > _______________________________________________ > 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" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Tue Oct 17 10:17:51 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 8928CE3553D for ; Tue, 17 Oct 2017 10:17:51 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F7C166A41 for ; Tue, 17 Oct 2017 10:17:50 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1508235468; s=domk; d=obsigna.com; h=To:References:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From: Subject:Mime-Version:Content-Type; bh=4NZIdQIsCY6KOBqfuBthSHoA8csQCBR8M1KsA8LPlXk=; b=P5p3+YTrbBoueg2lbJfPZle/kWZ5Wl6tdh//r5CKkloO47QIbl7z8iSabtt3iqoIys sfW18pVvyQ2GyivwNudxBH7f+OqnolrGHFe9V4dp02JVajcbzBZJnlGxKw0n+u/CIpfj vtgiLsPTIufoOzgW0gvkzXiJsJNTQ92VM+x/M= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhS0fwIz0hhE+lDkJmR/zkZ585QgNmUK62cRj/0nG X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (bb02b41e.virtua.com.br [187.2.180.30]) by smtp.strato.de (RZmta 42.6 DYNA|AUTH) with ESMTPSA id 4014e1t9HAHlCGM (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Tue, 17 Oct 2017 12:17:47 +0200 (CEST) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 74D651350F919; Tue, 17 Oct 2017 08:17:44 -0200 (BRST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: FreeBSD 12-CURRENT-ARMv7 and the BeagleBone Black From: "Dr. Rolf Jansen" In-Reply-To: <20171016220137.7d9257804b39cb9f5a6587aa@bidouilliste.com> Date: Tue, 17 Oct 2017 08:17:44 -0200 Content-Transfer-Encoding: quoted-printable Message-Id: <7E941B26-A0D9-4854-AEFB-F27956BE948F@obsigna.com> References: <390DFE72-FE55-405E-831F-7892EF039B52@obsigna.com> <20171016220137.7d9257804b39cb9f5a6587aa@bidouilliste.com> To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) 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: Tue, 17 Oct 2017 10:17:51 -0000 > Am 16.10.2017 um 18:01 schrieb Emmanuel Vadot : > On Mon, 16 Oct 2017 17:54:48 -0200 "Dr. Rolf Jansen" = wrote: >=20 >> I saw the first ARMv7 snapshot images (Pandaboard and Hummingboard) = arrived on the FreeBSD ftp server. >>=20 >> AFAIK, the BBB is ARMv7 as well. I am going to setup a new system on = a BeagleBone Black, and I am wondering whether I want to stay with the = 12-CURRENT-ARMv6 like my other setups, or whether it would be a good = idea to install a 12-CURRENT-ARMv7. >>=20 >> Questions: >> - would the ARMv7 flavor of FreeBSD run on a BeagleBone Black? >=20 > Yes, Glen (gjb@) already made the switch for the releases snapshot for = that. >=20 >> - if yes, will snapshots of 12-CURRENT-ARMv7 be available for the = BeagleBone in a foreseeable future? >=20 > See above. >=20 >> - can I expect any advantages (disadvantages) from the ARMv7 = architecture compared to the ARMv6 one? >=20 > Maybe not right now but with packages/ports stuff dealt by Mark = Linimon, mmel@ and miki yes probably. Emmanuel, thank you very much for your reply. For sure, I will give the = upcomming BBB-ARMv7 snapshot a try. Best regards Rolf= From owner-freebsd-arm@freebsd.org Thu Oct 19 00:04:52 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 A3CDAE476BB for ; Thu, 19 Oct 2017 00:04:52 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88E3D6F76B for ; Thu, 19 Oct 2017 00:04:52 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id C68078ECB; Thu, 19 Oct 2017 00:04:51 +0000 (UTC) From: Jan Beich To: freebsd-arm@freebsd.org Subject: AT_HWCAP support on aarch64 Date: Thu, 19 Oct 2017 02:04:46 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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, 19 Oct 2017 00:04:52 -0000 armv6 and armv7 recently gained support to check NEON or VFP* at runtime. However, some ports want to take advantage of AES, CRC32, SHA1, SHA256 acceleration on aarch64 as well. Do you plan to support any HWCAP_* for AT_HWCAP on aarch64? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223016 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223019 (ditto Chromium) http://elixir.free-electrons.com/linux/latest/source/arch/arm64/include/uapi/asm/hwcap.h From owner-freebsd-arm@freebsd.org Thu Oct 19 01:40:24 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 5C5FDE49468 for ; Thu, 19 Oct 2017 01:40:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1583572144 for ; Thu, 19 Oct 2017 01:40:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9J1eQxY003943 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Oct 2017 18:40:27 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9J1eQm0003942; Wed, 18 Oct 2017 18:40:26 -0700 (PDT) (envelope-from fbsd) Date: Wed, 18 Oct 2017 18:40:26 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171019014026.GA3887@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171016035716.GA92612@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171016035716.GA92612@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) 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, 19 Oct 2017 01:40:24 -0000 Using the old v6 kernel to build a new v7 world finally worked, after a pmap panic was worked around. Rebooted to the v7 kernel and ran installworld in single user, with the following error: strip: elf_begin() failed: Invalid argument install: strip command strip failed on //usr/bin/clang The double slash looks like it might be a typo. After going to multi-user it looks as if clang didn't install at all. If someone can suggest a workaround it would be much appreciated. Thanks for reading! bob prohaska On Sun, Oct 15, 2017 at 08:57:17PM -0700, bob prohaska wrote: > With the kernel at r324562, /usr/src at r324599, /usr/src/Makefile.inc1 > showing > #.if make(buildworld) > #BUILD_ARCH!= uname -p > BUILD_ARCH!= echo armv7 > #.if ${MACHINE_ARCH} != ${BUILD_ARCH} > #.error To cross-build, set TARGET_ARCH. > #.endif > #.endif > and /etc/make.conf containing > > KERNCONF=RPI2 > TARGET=arm > TARGET_ARCH=armv7 > DESTDIR=/ > > make buildworld ran until it crashed with a PT2MAP panic, as it has done > many times before. The log file reached 26 MB, it probably had to go a > little over 30 MB to finish. > > The console, top and logfile are at > http://www.zefox.net/~fbsd/rpi2/crashes/crash_10_15_17/ > > The machine has been rebooted to a v6 kernel which has built world > in the past, r322520, though it too has crashed with PT2MAP errors > at least once. /usr/src/Makefile.inc1 has been restored and buildworld > restarted with > make -j4 buildworld TARGET_ARCH=armv7 > buildworld.log & > There are no immediate errors, I'll let the build run unless > someone suggests a reason to try something else. > > The reply threads have become somewhat tangled, I'll trim here > for sake of brevity. > > Thanks for reading!! > > bob prohaska > From owner-freebsd-arm@freebsd.org Thu Oct 19 21:25:55 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 28FE0E47D35 for ; Thu, 19 Oct 2017 21:25:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17A5981689 for ; Thu, 19 Oct 2017 21:25:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9JLPsiN004214 for ; Thu, 19 Oct 2017 21:25:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 223119] libc++experimental was disabled for arm but now builds fine. Date: Thu, 19 Oct 2017 21:25:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: gabdelmalik@uniridge.com.au X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 19 Oct 2017 21:25:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223119 Bug ID: 223119 Summary: libc++experimental was disabled for arm but now builds fine. Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: gabdelmalik@uniridge.com.au Back in May libc++experimental was hooked into the build however disabled f= or arm and mips due to compilation failure. I've just successfully built the library for svn revision 323729. This is p= ost the import of Clang 5.0 which occurred in late July. The only conclusion I can make from this is that the original issue has been fixed by that subsequent release. It would be great to have it hooked up again for arm, I can't say anything = for mips as I don't run that platform. My local patch is below. Thanks for your attention. Regards, George. Index: lib/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- lib/Makefile (revision 323729) +++ lib/Makefile (working copy) @@ -158,7 +158,7 @@ .if ${MK_LIBCPLUSPLUS} !=3D "no" _libcxxrt=3D libcxxrt _libcplusplus=3D libc++ -.if ${MACHINE_CPUARCH} !=3D "arm" && ${MACHINE_CPUARCH} !=3D "mips" +.if ${MACHINE_CPUARCH} !=3D "mips" _libcplusplus+=3D libc++experimental .endif .endif --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Thu Oct 19 23:26:00 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 E547FE49E12 for ; Thu, 19 Oct 2017 23:26:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5B9684B87; Thu, 19 Oct 2017 23:26:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 8AC3810A7DB; Thu, 19 Oct 2017 19:25:57 -0400 (EDT) From: John Baldwin To: freebsd-arm@freebsd.org Cc: Jan Beich Subject: Re: AT_HWCAP support on aarch64 Date: Thu, 19 Oct 2017 11:30:57 -0700 Message-ID: <3317147.pUqZiAYRoN@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 19 Oct 2017 19:25:57 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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, 19 Oct 2017 23:26:01 -0000 On Thursday, October 19, 2017 02:04:46 AM Jan Beich wrote: > armv6 and armv7 recently gained support to check NEON or VFP* at runtime. > However, some ports want to take advantage of AES, CRC32, SHA1, SHA256 > acceleration on aarch64 as well. > > Do you plan to support any HWCAP_* for AT_HWCAP on aarch64? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223016 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223019 (ditto Chromium) > http://elixir.free-electrons.com/linux/latest/source/arch/arm64/include/uapi/asm/hwcap.h I think there is certainly a desire to do so, it should just be a matter of populating a hwcap variable and setting it in sysentvec. -- John Baldwin From owner-freebsd-arm@freebsd.org Fri Oct 20 05:08:47 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 73B2EE4FE0A for ; Fri, 20 Oct 2017 05:08:47 +0000 (UTC) (envelope-from jon@brawn.org) Received: from ahs1.r4l.com (ahs1.r4l.com [198.27.81.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 487126816A for ; Fri, 20 Oct 2017 05:08:46 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=To:Date:Message-Id:Subject:Mime-Version:Content-Type:From: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=LYB+eeW8XL/RF10EVwDO0fmGHZ+GNg1rHS9+gPcEMX8=; b=w7rXjGk2BMHS/sSB7puoIWa4N4 tZn7UA/Cv3TjK0BnJkNrx4PR3Nb4xwN8HCwxKAY6sng53PArNz7gFhdhV60jrBDe4+3NBgnvz9Ofx 8OBHm+krM/5w2/SYPXhaYrc6uZKNpsCOoprosHTbcKmgmQOyLyMiw4YyD1urMXwfQxU571XAMeAz+ I3UIAyVBG5QVG0emfjCOh9R7Udg+IQJhV3iW0hBagjoh4trKez55MryOCSxKVdhjrkzolnqhPaT4h d9wLEg5DnDCOLAMBA1CTzOb8kS3i523lMbfbXE/pu6JgyzUvly+7mRc+TqHL71a9XDiA/5BTWMZ0M 1zSvEP+g==; Received: from [136.62.171.86] (port=55980 helo=[192.168.1.159]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1e5OsV-001roy-FW for freebsd-arm@freebsd.org; Fri, 20 Oct 2017 00:25:47 -0400 From: Jon Brawn Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Spot of bother compiling an ARMv8 kernel... Message-Id: Date: Thu, 19 Oct 2017 23:25:45 -0500 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: 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: Fri, 20 Oct 2017 05:08:47 -0000 Wotcha! I=E2=80=99ve got use of a SoftIron OverDrive 1000, and I thought it was = about time I updated it to a newer version of 12.0 CURRENT, so I = dutifully downloaded the mini memory stick image, installed all the = options that the installer offers, rebooted off of the hard drive, and = decided that the first thing that one has to do with a new system is = build a spangly new kernel. So: root@brax:/usr/src # make TARGET=3Darm64 TARGET_ARCH=3Daarch64 = KERNCONF=3DGENERIC-NODEBUG kernel And off it went. Then, alas, it stopped: cc -target aarch64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/tmp = -B/usr/obj/usr/src/tmp/usr/bin -c -O3 -pipe -fno-strict-aliasing -Werror = -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -include = /usr/obj/usr/src/sys/GENERIC-NODEBUG/opt_global.h -I. -I/usr/src/sys = -fno-common -g -fPIC -I/usr/obj/usr/src/sys/GENERIC-NODEBUG -ffixed-x18 = -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall = -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -std=3Diso9899:1999 -Werror = -march=3Darmv8-a+crypto /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: /usr/lib/clang/5.0.0/include/arm_neon.h:31:10: fatal error: 'stdint.h' = file not found #include ^~~~~~~~~~ 1 error generated. *** Error code 1 Stop. What is the freebsd-arm protocol for dealing with this kind of issue? Do = I file a bugzilla on it? Or just ask nicely on this list, and someone = will say, =E2=80=9CAh, yes, you need to install and everything = will be alright. Must remember to put that on my to-do list!=E2=80=9D? I = can work around it easily enough using =E2=80=9CThe Mark Of Brawn=E2=80=9D= (what others might call, less charitably, =E2=80=9Ca bodge=E2=80=9D). Jon.= From owner-freebsd-arm@freebsd.org Fri Oct 20 05:32:20 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 64467E50429 for ; Fri, 20 Oct 2017 05:32:20 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-80.reflexion.net [208.70.210.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 191F76922A for ; Fri, 20 Oct 2017 05:32:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 5398 invoked from network); 20 Oct 2017 05:32:12 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Oct 2017 05:32:12 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 20 Oct 2017 01:32:12 -0400 (EDT) Received: (qmail 31131 invoked from network); 20 Oct 2017 05:32:12 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Oct 2017 05:32:12 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id B9794EC8166; Thu, 19 Oct 2017 22:32:11 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Spot of bother compiling an ARMv8 kernel... Date: Thu, 19 Oct 2017 22:32:10 -0700 References: To: Jon Brawn , freebsd-arm , FreeBSD Toolchain In-Reply-To: Message-Id: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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, 20 Oct 2017 05:32:20 -0000 On 2017-Oct-19, at 9:25 PM, Jon Brawn wrote: . . . > root@brax:/usr/src # make TARGET=3Darm64 TARGET_ARCH=3Daarch64 = KERNCONF=3DGENERIC-NODEBUG kernel >=20 > And off it went. >=20 > Then, alas, it stopped: >=20 > cc -target aarch64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/tmp = -B/usr/obj/usr/src/tmp/usr/bin -c -O3 -pipe -fno-strict-aliasing -Werror = -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -include = /usr/obj/usr/src/sys/GENERIC-NODEBUG/opt_global.h -I. -I/usr/src/sys = -fno-common -g -fPIC -I/usr/obj/usr/src/sys/GENERIC-NODEBUG -ffixed-x18 = -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall = -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -std=3Diso9899:1999 -Werror = -march=3Darmv8-a+crypto /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c > In file included from = /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: > /usr/lib/clang/5.0.0/include/arm_neon.h:31:10: fatal error: 'stdint.h' = file not > found > #include > ^~~~~~~~~~ > 1 error generated. > *** Error code 1 . . . See also: bugzilla 220125 from back in 2017-Jun-19. Normally the kernel does not depend on stdint.h but for this arm NOEN code it does. make . . . buildworld buildkernel would work: the buildworld would put the stdint.h in a place where the buidlkernel would find it. Unfortunately, make . . . kernel-toolchain make . . . buildkernel would not put the stdint.h in a place that buildkernel would fine it --and, so, it would error out the same way. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Fri Oct 20 18:46:11 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 E12AAE3D2FD for ; Fri, 20 Oct 2017 18:46:11 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from bouvier.getmail.no (bouvier.getmail.no [84.210.184.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D9712911 for ; Fri, 20 Oct 2017 18:46:11 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 41BAF501D7 for ; Fri, 20 Oct 2017 20:39:16 +0200 (CEST) Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 6qt_yN9YEr6n for ; Fri, 20 Oct 2017 20:39:15 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id CA5B7501EA for ; Fri, 20 Oct 2017 20:39:15 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 bouvier.getmail.no CA5B7501EA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1508524755; bh=u1eWw36jPmv29eyXxSZPIWvwYx8UJjt4M9rgHFiaKCw=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=aAUFjaF4WaitSzL1FeIh7R/mxdWXtjYSt2ORlafusGFi87kR9XvxAFTFUm8HKzYZ8 Dqla8TThJRtiVRNwcK9XGzBiNtgQnBTuMxp956Hwd7HB68SH0jIv9MKV1UV9JYIYsG nsYrUhW/p/qVTI3QLE5HnJLFu9aQkWIFygohbXnY= X-Virus-Scanned: amavisd-new at bouvier.get.c.bitbit.net Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Eay_11G8yJe1 for ; Fri, 20 Oct 2017 20:39:15 +0200 (CEST) Received: from kg-core1.kg4.no (cm-84.209.39.108.getinternet.no [84.209.39.108]) by bouvier.getmail.no (Postfix) with ESMTPSA id 9E376501D7 for ; Fri, 20 Oct 2017 20:39:15 +0200 (CEST) Date: Fri, 20 Oct 2017 20:39:15 +0200 From: Torfinn Ingolfsen To: freebsd-arm@FreeBSD.org Subject: Re: Spot of bother compiling an ARMv8 kernel... Message-Id: <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> In-Reply-To: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> References: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 20 Oct 2017 18:46:12 -0000 On Thu, 19 Oct 2017 22:32:10 -0700 Mark Millard wrote: > > make . . . buildworld buildkernel > As a general thing; isn't buildworld before buildkernel a requirement on FreeBSD? -- Torfinn Ingolfsen From owner-freebsd-arm@freebsd.org Fri Oct 20 19:00:25 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 36757E3D654 for ; Fri, 20 Oct 2017 19:00:25 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8EB92E97 for ; Fri, 20 Oct 2017 19:00:24 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 23662 invoked from network); 20 Oct 2017 19:00:23 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Oct 2017 19:00:23 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 20 Oct 2017 15:00:23 -0400 (EDT) Received: (qmail 12702 invoked from network); 20 Oct 2017 19:00:22 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Oct 2017 19:00:22 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 510CAEC8804; Fri, 20 Oct 2017 12:00:22 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Spot of bother compiling an ARMv8 kernel... Date: Fri, 20 Oct 2017 12:00:21 -0700 References: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> To: Torfinn Ingolfsen , freebsd-arm@FreeBSD.org, FreeBSD Toolchain In-Reply-To: <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> Message-Id: <762393B5-E557-4F49-9CB0-41F9470BC623@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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, 20 Oct 2017 19:00:25 -0000 On 2017-Oct-20, at 11:39 AM, Torfinn Ingolfsen wrote: > On Thu, 19 Oct 2017 22:32:10 -0700 > Mark Millard wrote: >=20 >>=20 >> make . . . buildworld buildkernel >>=20 >=20 > As a general thing; isn't buildworld before buildkernel a requirement = on FreeBSD? There is (supposed to be) a faster alternative that is probably of interest primarily to folks working in/on the kernel or that have reasons to only build the kernel (or multiple variations of the kernel): make . . . kernel-toolchain make . . . buildkernel /usr/src/Makefile has the comment lines that I quote below, look at the last that I quote: # buildworld - Rebuild *everything*, including glue to help do # upgrades. # installworld - Install everything built by "buildworld". # world - buildworld + installworld, no kernel. # buildkernel - Rebuild the kernel and the kernel-modules. # installkernel - Install the kernel and the kernel-modules. # installkernel.debug # reinstallkernel - Reinstall the kernel and the kernel-modules. # reinstallkernel.debug # kernel - buildkernel + installkernel. # kernel-toolchain - Builds the subset of world necessary to build a = kernel Right now kernel-toolchain and the aarch64 kernel source are not matched sufficiently for the sequence to work. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 21 01:50:34 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 25CD4E463B1 for ; Sat, 21 Oct 2017 01:50:34 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (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 CF6516D6EC for ; Sat, 21 Oct 2017 01:50:33 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by mail-qt0-x242.google.com with SMTP id d9so13776927qtd.7 for ; Fri, 20 Oct 2017 18:50:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version; bh=Nn+o/HePvl4PRZXH607+sJg0w0yGkD3TBX0F4Ts0oig=; b=Fxt/k/Sui7z2GRmny7GnGNzVufB4LjV836r0qm/xfuwSGTZKxj8GOfXt7bizaB7xYU eYXl/zOYhAeDwIqpsQqCx3INeDdUagIYklnAXTGmU2LyP/0mC2zuW/6sh9QnejAvwKIP 4cgrh1Sxtql4C++EZvud8bm+7ztJGUgTpKwbeTMkN2u+LeTokULtH5HQu81o07sNCMgy xrPvSR9hDxCmwLjl7Nc4+UFVwMY6EwVm8M50zm1Ciu155X5O9fLX+2k1ioASEcvR+FbA 8IQg8HwLxhUTUrGY3AemRxqZ4uT784axCor/e3eeef8MNe75/7jmiqgAUriegpkLsOZf WYUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version; bh=Nn+o/HePvl4PRZXH607+sJg0w0yGkD3TBX0F4Ts0oig=; b=onrmMYf6LwNreByQd+ZfBT1jH1m1eey3LOLH7cunXNcHVFbnjjidbmgWb8QX0tX5tU 4Iblre+KR9RBr+/L8+Vm8HR4NUnkqIXXVFIn56wBl6WyIJJjCACLRMnQzmuwBnby5xhT 7BG/kgTCVWETsXkb7hSS5Ixu/n0wpoPJiUa0ogzN+ubp4MDBeUljVruuGJj4YcacNxMW ZNUuLmUM6G0sdcUlKZu7rQ6ffEMmZyTP2YVa//LXe0GUZVO+10Ge41ZSyRcwIBbPGKl3 NemzgB31Fx4S9z8S/ZptS+1jAqwuU5EI1jjHIb1E84TGPecTZ11A48yrb1N4iXfIqze4 SB8w== X-Gm-Message-State: AMCzsaW1pzQnuqxowP1UIEk8936rSzkUqAc8FUinPFnjXzEcO0fq01iy c9pSP3wx6Xp5E+hdXZ8jkqM= X-Google-Smtp-Source: ABhQp+Szs4Mn8FsNS/N0VDdej8Dmfl1COT9DjdB1aup6yQRJbOkfapt4HDlYr2kxHdcHGsMuPzQtlA== X-Received: by 10.237.53.13 with SMTP id a13mr9936700qte.250.1508550632777; Fri, 20 Oct 2017 18:50:32 -0700 (PDT) Received: from kan ([2601:18f:802:4680:226:18ff:fe00:232e]) by smtp.gmail.com with ESMTPSA id k2sm1438566qth.83.2017.10.20.18.50.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 20 Oct 2017 18:50:31 -0700 (PDT) Date: Fri, 20 Oct 2017 21:50:22 -0400 From: Alexander Kabaev To: Torfinn Ingolfsen Cc: freebsd-arm@FreeBSD.org Subject: Re: Spot of bother compiling an ARMv8 kernel... Message-ID: <20171020215022.642441bf@kan> In-Reply-To: <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> References: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/1ZeGYZcqlMwk4GSVv+cdDp8"; protocol="application/pgp-signature" 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: Sat, 21 Oct 2017 01:50:34 -0000 --Sig_/1ZeGYZcqlMwk4GSVv+cdDp8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 20 Oct 2017 20:39:15 +0200 Torfinn Ingolfsen wrote: > On Thu, 19 Oct 2017 22:32:10 -0700 > Mark Millard wrote: >=20 > >=20 > > make . . . buildworld buildkernel > > =20 >=20 > As a general thing; isn't buildworld before buildkernel a requirement > on FreeBSD? --=20 > Torfinn Ingolfsen No. make kernel-toolchain should be enough to get the pre-requisites. --=20 Alexander Kabaev --Sig_/1ZeGYZcqlMwk4GSVv+cdDp8 Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEExffZlZm2QeE8UVaRBxMimZJ5Ln4FAlnqp+BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM1 RjdEOTk1OTlCNjQxRTEzQzUxNTY5MTA3MTMyMjk5OTI3OTJFN0UACgkQBxMimZJ5 Ln60yA/+LCEuHcJgqpZ8LLtVlo34ayUMTU0fTeFpKnkAk3Z1IezVogsl5JV4OsVW 4G9XI8RsVlGj6DeBQpNQGT9T5onfQw+cKufGRykV8yQCWIX/Y2tLU/RUmrnnx5yQ bV5icCriuabwnLPh40I9ocR0Ap+j+WOaNOPeevAXxSIL40IN2TgKxYl5lMDW2NhN WnvwOjBlmKSOL6vf/nBzt76Wr4b/WMCxPvkKEjbu5yC/bfYiTWrD86OUp/IMRJ3V kFWOLWh4rEbLIzyalrrKnWjkfN7DMIq8YWkr+wQPmzAsRPamogVDmvQC++/iWLAc vadJWpfEma3fQteoeBSrfF1Ec8YCwJ4BcHmd9NEbAAGuLRaM3R+2o/4YYJN5izT3 osxj1AhExTMh5SzSSleNMSRV13SF9gqRYo8j5KC9I+CMwEIVRmzOQGOv8+QyKKvN f7P5MjDCxsVZl6F5nUn/xtdznSnOrF+i8EJF+DQT6RwQQaBmHq9smqTomPEtiKMK pkdooHmIuSK9J2zKzoz/YdMjxdX+lIt6vvK/P7Jx0j00x+KU3Mjs3JOxnUt04cbZ n6KCzOnFHCbjAaJw0ZP/+s8WioxPKanxEpFTIDheQHkp+KQDLk8XZA+JufeT9g4H 79YuLG9ckTn6VRV9Hfl+iB4FYdEWxzqjF9GwUJLE3IZEZz4nmls= =64Bg -----END PGP SIGNATURE----- --Sig_/1ZeGYZcqlMwk4GSVv+cdDp8-- From owner-freebsd-arm@freebsd.org Sat Oct 21 02:00:22 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 8072BE46A70 for ; Sat, 21 Oct 2017 02:00:22 +0000 (UTC) (envelope-from jon@brawn.org) Received: from ahs1.r4l.com (ahs1.r4l.com [198.27.81.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 556C86DBC1 for ; Sat, 21 Oct 2017 02:00:21 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=Message-Id:In-Reply-To:To:References:Date:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=SAV15P5pdBtjwdeIT9gCuW4AuvhKreOMFOxvPqfCJ7k=; b=xrSazDFSAZqr0c06bXjfPQvPvF EvoDYGIXuQ5MFriq40Oe34VoEh/ZTUPQq7FANG/NeJDSBLBIJr3Z88ba1kiC/5avFYZd8y2xQhlHf pLj17F0y2G0h7ppQA8oJ6LjV4m24F6O6LIo2feqrD5AHhCUn1FY5deUw86B4jgtBGjjD1so6hhdq7 Hu3W8SEuw/aUeaLqc0IlxHq2x3CV/M2zQyE7st27wwHmEkH03iQvSLK+5fBp6pLvz120SCDmTdl+o yqT2yOaIesWqO4mqK4EMiI0CF1O3lkSp1pwfmZXgzwNCB41XLLY3h9kHF1tCpcfTJrjmMLEndaj7E w0+o5K6A==; Received: from [136.62.171.86] (port=61562 helo=[192.168.1.159]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1e5j5F-004KDE-VU for freebsd-arm@freebsd.org; Fri, 20 Oct 2017 22:00:18 -0400 From: Jon Brawn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Spot of bother compiling an ARMv8 kernel... Date: Fri, 20 Oct 2017 21:00:16 -0500 References: To: freebsd-arm@freebsd.org In-Reply-To: Message-Id: <50540920-3CE1-477B-A820-5226E0D71477@brawn.org> X-Mailer: Apple Mail (2.3273) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: 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: Sat, 21 Oct 2017 02:00:22 -0000 Thanks to all that replied - buildworld before buildkernel does indeed = work. Jon. > On Oct 19, 2017, at 11:25 PM, Jon Brawn wrote: >=20 > Wotcha! >=20 > I=E2=80=99ve got use of a SoftIron OverDrive 1000, and I thought it = was about time I updated it to a newer version of 12.0 CURRENT, so I = dutifully downloaded the mini memory stick image, installed all the = options that the installer offers, rebooted off of the hard drive, and = decided that the first thing that one has to do with a new system is = build a spangly new kernel. >=20 > So: >=20 > root@brax:/usr/src # make TARGET=3Darm64 TARGET_ARCH=3Daarch64 = KERNCONF=3DGENERIC-NODEBUG kernel >=20 > And off it went. >=20 > Then, alas, it stopped: >=20 > cc -target aarch64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/tmp = -B/usr/obj/usr/src/tmp/usr/bin -c -O3 -pipe -fno-strict-aliasing -Werror = -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -include = /usr/obj/usr/src/sys/GENERIC-NODEBUG/opt_global.h -I. -I/usr/src/sys = -fno-common -g -fPIC -I/usr/obj/usr/src/sys/GENERIC-NODEBUG -ffixed-x18 = -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall = -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -std=3Diso9899:1999 -Werror = -march=3Darmv8-a+crypto /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c > In file included from = /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: > /usr/lib/clang/5.0.0/include/arm_neon.h:31:10: fatal error: 'stdint.h' = file not > found > #include > ^~~~~~~~~~ > 1 error generated. > *** Error code 1 >=20 > Stop. >=20 > What is the freebsd-arm protocol for dealing with this kind of issue? = Do I file a bugzilla on it? Or just ask nicely on this list, and someone = will say, =E2=80=9CAh, yes, you need to install and everything = will be alright. Must remember to put that on my to-do list!=E2=80=9D? I = can work around it easily enough using =E2=80=9CThe Mark Of Brawn=E2=80=9D= (what others might call, less charitably, =E2=80=9Ca bodge=E2=80=9D). >=20 > Jon. > _______________________________________________ > 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" From owner-freebsd-arm@freebsd.org Sat Oct 21 04:38:57 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 76620E4CCB8 for ; Sat, 21 Oct 2017 04:38:57 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::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 EF87272DB0 for ; Sat, 21 Oct 2017 04:38:56 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id k40so15086228lfi.4 for ; Fri, 20 Oct 2017 21:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4EqvQX+ooiO5q1m6+IoLjwKSzqC2frgJk5RRumtF98Y=; b=YO8S1GswfhunjhQwYdlX9z/nQLmkU4ylXdr85wVu74kUmaZ6PC5dVSY4QQ13mDbxGU ldXpZOycImTjk3jLQZRGA3wAmxJAh5szITdnt5V5J4+ae0ovqk+3sJQzayDiADYep0Qe JuK+ysllUepQhEfk7EsZv8GcHO33cE/3Vr0ppGMbtATLFDfaxxFtzV3IhPhYfJZ+eMoe YZhHJG2C3vpaZ6As6iBuMkXfZZcm0rxcXImmn4jSYxcHCivkc2Szmy0uGXX/8h4jF/42 qswIPCKpdTTYKuyQ4WbHo0TJJPNOK5KwFkV5JCv1NSxKH1H1BLiEpakpayYy9fP1Hv3e PZYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4EqvQX+ooiO5q1m6+IoLjwKSzqC2frgJk5RRumtF98Y=; b=mVsp0ffxbRUhs/hbOsSGK5FTRkfIlZPbQTibmFmBB1zxmaoefHpHotzo2Zla9qjafs qZe2Agj1EMcgAAHLmwW2tDtSynKnOJMOKXA9bEb4dr6RD+5ms1Y+RZcRU7k7m/3mdlCF X8cjUFxzqoonlxbYE7Ey4c4DyZV9B/F+mkxWqZQSZjAm5+lmNKEdmGyzp+d8JgJOC4rL AebRS3QUC/c08LUNaMAbbKxH2iGXfDUqydWZtW+oUt7BfL47Ii+F4o6Osxqad21Edynf oyuSa0tOEmAstH9hQ5G723lXc88PfobGzFXuclyYtPsr05aFG4RGoTmPC2zaHinnzbtf 3i3g== X-Gm-Message-State: AMCzsaXyCMSo4XlH0epA28qOjyVqd+e7xSt2/qN2ijZUqK7iBn+Um1RL i0zcAkCjclfIdR8Vx2CEflEfPY1OCbH+0M+7Clk= X-Google-Smtp-Source: ABhQp+SSXiJ58Wxc2gDLF8Y642ULesH4nHX3z2t6CutpGLEYETDvPExLrXFqdDlzRCPYmJIIl6MSBU7zzzR8COCrMl0= X-Received: by 10.46.21.2 with SMTP id s2mr2807656ljd.71.1508560733715; Fri, 20 Oct 2017 21:38:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.14.1 with HTTP; Fri, 20 Oct 2017 21:38:52 -0700 (PDT) In-Reply-To: <50540920-3CE1-477B-A820-5226E0D71477@brawn.org> References: <50540920-3CE1-477B-A820-5226E0D71477@brawn.org> From: Russell Haley Date: Fri, 20 Oct 2017 21:38:52 -0700 Message-ID: Subject: Re: Spot of bother compiling an ARMv8 kernel... To: Jon Brawn Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Sat, 21 Oct 2017 04:38:57 -0000 On Fri, Oct 20, 2017 at 7:00 PM, Jon Brawn wrote: > Thanks to all that replied - buildworld before buildkernel does indeed wo= rk. > > Jon. > >> On Oct 19, 2017, at 11:25 PM, Jon Brawn wrote: >> >> Wotcha! >> >> I=E2=80=99ve got use of a SoftIron OverDrive 1000, and I thought it was = about time I updated it to a newer version of 12.0 CURRENT, so I dutifully = downloaded the mini memory stick image, installed all the options that the = installer offers, rebooted off of the hard drive, and decided that the firs= t thing that one has to do with a new system is build a spangly new kernel. >> >> So: >> >> root@brax:/usr/src # make TARGET=3Darm64 TARGET_ARCH=3Daarch64 KERNCONF= =3DGENERIC-NODEBUG kernel >> >> And off it went. >> >> Then, alas, it stopped: >> >> cc -target aarch64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/tmp = -B/usr/obj/usr/src/tmp/usr/bin -c -O3 -pipe -fno-strict-aliasing -Werror -D= _KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src= /sys/GENERIC-NODEBUG/opt_global.h -I. -I/usr/src/sys -fno-common -g -fPIC -= I/usr/obj/usr/src/sys/GENERIC-NODEBUG -ffixed-x18 -ffreestanding -fwrapv -f= stack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict= -prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wund= ef -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ -Wmissing-include-d= irs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-= compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-un= used-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-= error-address-of-packed-member -std=3Diso9899:1999 -Werror -march=3Darmv= 8-a+crypto /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c >> In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: >> /usr/lib/clang/5.0.0/include/arm_neon.h:31:10: fatal error: 'stdint.h' f= ile not >> found >> #include >> ^~~~~~~~~~ >> 1 error generated. >> *** Error code 1 >> >> Stop. >> >> What is the freebsd-arm protocol for dealing with this kind of issue? Do= I file a bugzilla on it? Or just ask nicely on this list, and someone will= say, =E2=80=9CAh, yes, you need to install and everything will be= alright. Must remember to put that on my to-do list!=E2=80=9D? I can work = around it easily enough using =E2=80=9CThe Mark Of Brawn=E2=80=9D (what oth= ers might call, less charitably, =E2=80=9Ca bodge=E2=80=9D). I think you already knew that and just wanted to throw your cool last name around. :P Come again, I enjoyed your email! Russ(a hanger-on) >> Jon. >> _______________________________________________ >> 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" > > _______________________________________________ > 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" From owner-freebsd-arm@freebsd.org Sat Oct 21 12:51:53 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 A90AEE55A26 for ; Sat, 21 Oct 2017 12:51:53 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from lamora.getmail.no (lamora.getmail.no [84.210.184.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E2B2835B1 for ; Sat, 21 Oct 2017 12:51:53 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id 9F05D125589 for ; Sat, 21 Oct 2017 14:38:25 +0200 (CEST) Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id wAK5k6jtJlmS for ; Sat, 21 Oct 2017 14:38:25 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id 2DF5B12558A for ; Sat, 21 Oct 2017 14:38:25 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 lamora.getmail.no 2DF5B12558A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1508589505; bh=Z6UHB0mrc7bA8+1Ux7OgE3acsHvUKZdbEpc6AnIG8IY=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=kCuTiWEZOha15MDzaNOHuzqx3acyDisdB3QthlWaJQUuhj8ldA6Aab+A+bYgKwjNC 2yTstXCsSxWzVEzFsalwMfsVyDFp0feUIhZrJ0K8sWPJrrK5Bdv/LIzdtxUnOBHdLA MEZs7Dm39EXtl7oEqO+PLPWhhEobhIyO522F33wY= X-Virus-Scanned: amavisd-new at lamora.get.c.bitbit.net Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id idIoMIAtk629 for ; Sat, 21 Oct 2017 14:38:25 +0200 (CEST) Received: from kg-core1.kg4.no (cm-84.209.39.108.getinternet.no [84.209.39.108]) by lamora.getmail.no (Postfix) with ESMTPSA id E6F46125589 for ; Sat, 21 Oct 2017 14:38:24 +0200 (CEST) Date: Sat, 21 Oct 2017 14:38:24 +0200 From: Torfinn Ingolfsen To: freebsd-arm@FreeBSD.org Subject: Re: Spot of bother compiling an ARMv8 kernel... Message-Id: <20171021143824.487cb9cd6ef36e9542800ad5@getmail.no> In-Reply-To: <20171020215022.642441bf@kan> References: <63A81F33-4DAF-45A3-A19A-F83FE63DB331@dsl-only.net> <20171020203915.e92a6281a64eb30eca7f5457@getmail.no> <20171020215022.642441bf@kan> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Sat, 21 Oct 2017 12:51:53 -0000 On Fri, 20 Oct 2017 21:50:22 -0400 Alexander Kabaev wrote: > On Fri, 20 Oct 2017 20:39:15 +0200 > Torfinn Ingolfsen wrote: > > > On Thu, 19 Oct 2017 22:32:10 -0700 > > Mark Millard wrote: > > > > > > > > make . . . buildworld buildkernel > > > > > > > As a general thing; isn't buildworld before buildkernel a requirement > > on FreeBSD? -- > > Torfinn Ingolfsen > > No. make kernel-toolchain should be enough to get the pre-requisites. Than I learned something new today (I always do). Thanks! -- Torfinn Ingolfsen From owner-freebsd-arm@freebsd.org Sat Oct 21 15:51:44 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 65301E31ABF for ; Sat, 21 Oct 2017 15:51:44 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B28A3098 for ; Sat, 21 Oct 2017 15:51:43 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id 5vhleEGDR4UM75vhoeFUQZ; Sat, 21 Oct 2017 15:28:56 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id v9LFUQ8O014236 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 21 Oct 2017 11:30:27 -0400 (EDT) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] To: freebsd-arm@FreeBSD.org Reply-To: lausts@acm.org From: Thomas Laus Subject: Does FreeBSD-update work for ARM? Message-ID: Date: Sat, 21 Oct 2017 11:30:27 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfFtWUqn3dYg1GPMxEnjujPi2cPz+/jcIcb5HnebQwiHLIcZkN2H8wwMvJ19t8Fgx6D2aKIp9ELM28e4R6YOOuNMlSPIXvQQL8R3Q1kjrnDZQPffj+Is8 yYKXKwe/fi9V834l2mXdKfJ4Nyx17AaFJ5lDbJHra2kHvn1e7VVQeSc/ 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: Sat, 21 Oct 2017 15:51:44 -0000 I have a new 11.1 installation on a Beaglebone Black and wanted to install the two patches that have been issued since it's release. I receive the following dialog. root@beaglebone:/root # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update6.freebsd.org... failed. Fetching public key from update4.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. No mirrors remaining, giving up. My AMD64 that is also running Release 11.1 receives the patches with the same command and does not have an issue with the identical public key that is in /etc/freebsd-update.conf on both computers. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-arm@freebsd.org Sat Oct 21 17:46:57 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 735A7E34B72 for ; Sat, 21 Oct 2017 17:46:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2524F64FC4 for ; Sat, 21 Oct 2017 17:46:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24527 invoked from network); 21 Oct 2017 17:46:54 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 21 Oct 2017 17:46:54 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 21 Oct 2017 13:46:54 -0400 (EDT) Received: (qmail 18871 invoked from network); 21 Oct 2017 17:46:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Oct 2017 17:46:54 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 07901EC7B9D; Sat, 21 Oct 2017 10:46:54 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Message-Id: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> Date: Sat, 21 Oct 2017 10:46:53 -0700 To: Emmanuel Vadot , freebsd-arm X-Mailer: Apple Mail (2.3273) 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: Sat, 21 Oct 2017 17:46:57 -0000 > Author: manu > Date: Sat Oct 21 16:12:00 2017 > New Revision: 324822 > URL:=20 > https://svnweb.freebsd.org/changeset/base/324822 >=20 >=20 > Log: > dtb/allwinner: Disconnect sinovoip-bpi-m3.dts from the build > =20 > No active commiter have this board and we diverged too much from > the upstream DTS. Does this effectively mean dropping of support? Is sysutils/u-boot-sinovoip-bpi-m3 now defunct and to be removed at some point? (Personal note: Of the 2 types of armv7 boards that I generally have had access to this one had more RAM and, so, I preferred it.) > Modified: > head/sys/modules/dtb/allwinner/Makefile >=20 > Modified: head/sys/modules/dtb/allwinner/Makefile > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/sys/modules/dtb/allwinner/Makefile Sat Oct 21 15:48:16 2017 = (r324821) > +++ head/sys/modules/dtb/allwinner/Makefile Sat Oct 21 16:12:00 2017 = (r324822) > @@ -3,7 +3,6 @@ > DTS=3D \ > nanopi-neo.dts \ > orangepi-plus-2e.dts \ > - sinovoip-bpi-m3.dts \ > sun4i-a10-cubieboard.dts \ > sun4i-a10-olinuxino-lime.dts \ > sun6i-a31s-sinovoip-bpi-m2.dts \ =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 21 17:58:15 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 A1D0CE34DE0 for ; Sat, 21 Oct 2017 17:58:15 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 120266542D for ; Sat, 21 Oct 2017 17:58:14 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id a05003e2; Sat, 21 Oct 2017 19:58:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=OmFszOsUkFmjdI3OtoBtbjsj2WE=; b=qW9+lF9bP5wraLGy74GGk75jZFHE WUkVHL10hssk4Ug9HNaHHK4GZB2z/AXAeN3afWGpL/jqg1NJP2J09qfv6lhEwJ29 QRj4HYV/+5jPC3HTWH6tdp+YF/FGG7BoQAdDpVed1FZ5UFWsritEZ3BQGmM+gS3D MrLkzi75Jd4Ts90= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=WJ3CJGZyTZ7VguSjPwRmkMnM3Xgcw/yoOagpIfbyhaCCB3x5BepywChh DJBFELGgo2/h0utFXD1uauSusgOawUb7s2O3DET1sXV8WP8RS2KzlPA5il6u/NVX 8WVVkOg3hRAqzwOkuZIC7kvdP/DcZL2Tf7fF8uhDMta0tiHWBds= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id d83126e6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 21 Oct 2017 19:58:12 +0200 (CEST) Date: Sat, 21 Oct 2017 19:58:12 +0200 From: Emmanuel Vadot To: Mark Millard Cc: freebsd-arm Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Message-Id: <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> In-Reply-To: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> References: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Sat, 21 Oct 2017 17:58:15 -0000 On Sat, 21 Oct 2017 10:46:53 -0700 Mark Millard wrote: > > Author: manu > > Date: Sat Oct 21 16:12:00 2017 > > New Revision: 324822 > > URL: > > https://svnweb.freebsd.org/changeset/base/324822 > > > > > > Log: > > dtb/allwinner: Disconnect sinovoip-bpi-m3.dts from the build > > > > No active commiter have this board and we diverged too much from > > the upstream DTS. > > Does this effectively mean dropping of support? Is > sysutils/u-boot-sinovoip-bpi-m3 now defunct and to > be removed at some point? It means that A83T won't have any more commits from me (and in fact it never had), but if someone want to update our clock drivers to handle it I can help. For the ports, as long as it compile I won't remove it. > (Personal note: Of the 2 types of armv7 boards that I > generally have had access to this one had more RAM and, > so, I preferred it.) > -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Oct 21 18:27: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 9DB77E36A14 for ; Sat, 21 Oct 2017 18:27:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FCFC661D2 for ; Sat, 21 Oct 2017 18:27:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29365 invoked from network); 21 Oct 2017 18:26:58 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 21 Oct 2017 18:26:58 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 21 Oct 2017 14:26:58 -0400 (EDT) Received: (qmail 22149 invoked from network); 21 Oct 2017 18:26:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Oct 2017 18:26:58 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 0C8C0EC94E3; Sat, 21 Oct 2017 11:26:58 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Date: Sat, 21 Oct 2017 11:26:57 -0700 References: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> To: Emmanuel Vadot , freebsd-arm In-Reply-To: <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> Message-Id: X-Mailer: Apple Mail (2.3273) 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: Sat, 21 Oct 2017 18:27:06 -0000 On 2017-Oct-21, at 10:58 AM, Emmanuel Vadot wrote: > On Sat, 21 Oct 2017 10:46:53 -0700 > Mark Millard wrote: > >>> Author: manu >>> Date: Sat Oct 21 16:12:00 2017 >>> New Revision: 324822 >>> URL: >>> https://svnweb.freebsd.org/changeset/base/324822 >>> >>> >>> Log: >>> dtb/allwinner: Disconnect sinovoip-bpi-m3.dts from the build >>> >>> No active commiter have this board and we diverged too much from >>> the upstream DTS. >> >> Does this effectively mean dropping of support? Is >> sysutils/u-boot-sinovoip-bpi-m3 now defunct and to >> be removed at some point? > > It means that A83T won't have any more commits from me (and in fact it > never had), but if someone want to update our clock drivers to handle > it I can help. > For the ports, as long as it compile I won't remove it. If I understand the current status correctly, the recent changes to use upstream DTS materials took the BPI-M3 from having, e.g., USB working to USB not working. -r323641 removed AWUSBPHY_TYPE_A83T from enum awusbphy_type because of what was missing from upstream DTS materials and such. That is not a request: I'm just trying to be explicit about the overall status for reference for anyone else that was using BPI-M3's with FreeBSD. Feel free to correct or add to what I've reported if it is wrong/incomplete. Side note for Pine64+ 2GB status: By contrast Pine64+ 2GB's again support EHCI, at least on the lower USB port. (I've not tried the upper one.) My historical Pine64+ 2GB FreeBSD configuration works again as it used to: It is running -r324743 currently. Thanks Emmanuel. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 21 18:44:01 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 B0E0BE36F24 for ; Sat, 21 Oct 2017 18:44:01 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BFC666878 for ; Sat, 21 Oct 2017 18:44:00 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id c2063dde; Sat, 21 Oct 2017 20:43:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=w91woT2jSeHbELVCfmm1r3p8jxE=; b=bPgPTyZnJ/5ZtW94WfZlz4dvq+AD DMRfmgU71OybP+bxSnFWiXRssGgZeQPgVclw3bKXLJvuXjT922QKvia+TZS69cvz SY4TKncEMeC9waMJN4O+m83sO6ggOLpDQCw2+OAjN1mWwEnqsI/jf0sradOwb+5/ RA6Pi9InySvabAE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=HU/gwtEazcyqXKf6o1HzV+Q2lYZvzKyZ6LPrWaXiGjEecBVSljHgagkk HAobIceImJF26KbCTOvcLgLA9IDrxQZ5uktcsw2kA9e+6DbkMIix+ytm79dOlMhc 5WGZ28SvQOMVfHCoxxTHwg+d+ocz+4tUHuRFiAY+OIX1grAkkD4= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 348b7d2e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 21 Oct 2017 20:43:57 +0200 (CEST) Date: Sat, 21 Oct 2017 20:43:56 +0200 From: Emmanuel Vadot To: Mark Millard Cc: freebsd-arm Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Message-Id: <20171021204356.47e3cd6066144bcd07f46699@bidouilliste.com> In-Reply-To: References: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Sat, 21 Oct 2017 18:44:01 -0000 On Sat, 21 Oct 2017 11:26:57 -0700 Mark Millard wrote: > On 2017-Oct-21, at 10:58 AM, Emmanuel Vadot wrote: > > > On Sat, 21 Oct 2017 10:46:53 -0700 > > Mark Millard wrote: > > > >>> Author: manu > >>> Date: Sat Oct 21 16:12:00 2017 > >>> New Revision: 324822 > >>> URL: > >>> https://svnweb.freebsd.org/changeset/base/324822 > >>> > >>> > >>> Log: > >>> dtb/allwinner: Disconnect sinovoip-bpi-m3.dts from the build > >>> > >>> No active commiter have this board and we diverged too much from > >>> the upstream DTS. > >> > >> Does this effectively mean dropping of support? Is > >> sysutils/u-boot-sinovoip-bpi-m3 now defunct and to > >> be removed at some point? > > > > It means that A83T won't have any more commits from me (and in fact it > > never had), but if someone want to update our clock drivers to handle > > it I can help. > > For the ports, as long as it compile I won't remove it. > > If I understand the current status correctly, the > recent changes to use upstream DTS materials took > the BPI-M3 from having, e.g., USB working to USB > not working. -r323641 removed AWUSBPHY_TYPE_A83T > from enum awusbphy_type because of what was missing > from upstream DTS materials and such. Uses of upstream DTS is active since ~2 years ago. I think I removed support for USB on A83T because I couldn't test, but maybe the code just work and adding the compatible string again might do it. Feel free to send a patch on phabricator if it does. > That is not a request: I'm just trying to be > explicit about the overall status for reference > for anyone else that was using BPI-M3's with > FreeBSD. Feel free to correct or add to what > I've reported if it is wrong/incomplete. > > > Side note for Pine64+ 2GB status: > > By contrast Pine64+ 2GB's again support EHCI, > at least on the lower USB port. (I've not tried > the upper one.) My historical Pine64+ 2GB FreeBSD > configuration works again as it used to: It is > running -r324743 currently. Thanks Emmanuel. For the upper port we need a musb driver as it is binded to the OTG port (or patch the DTS but this will be wrong as in an hardware point of view the upper usb port is tied to the OTG port, not a standard usb one). Otherwise, glad to know that everything is working again for you on Pine64. Cheers, > === > Mark Millard > markmi at dsl-only.net -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Oct 21 21:06:08 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 8056FE3A40B for ; Sat, 21 Oct 2017 21:06:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F1966BD85 for ; Sat, 21 Oct 2017 21:06:07 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2684 invoked from network); 21 Oct 2017 21:06:06 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 21 Oct 2017 21:06:06 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 21 Oct 2017 17:06:06 -0400 (EDT) Received: (qmail 2388 invoked from network); 21 Oct 2017 21:06:05 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Oct 2017 21:06:05 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 4820AEC9045; Sat, 21 Oct 2017 14:06:05 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Date: Sat, 21 Oct 2017 14:06:04 -0700 References: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> <20171021204356.47e3cd6066144bcd07f46699@bidouilliste.com> To: Emmanuel Vadot , freebsd-arm In-Reply-To: <20171021204356.47e3cd6066144bcd07f46699@bidouilliste.com> Message-Id: <50728566-11C2-45EB-8367-00CAF38D4548@dsl-only.net> X-Mailer: Apple Mail (2.3273) 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: Sat, 21 Oct 2017 21:06:08 -0000 On 2017-Oct-21, at 11:43 AM, Emmanuel Vadot = wrote: > On Sat, 21 Oct 2017 11:26:57 -0700 > Mark Millard wrote: >=20 >> On 2017-Oct-21, at 10:58 AM, Emmanuel Vadot wrote: >>=20 >>>>> . . . >>=20 >> If I understand the current status correctly, the >> recent changes to use upstream DTS materials took >> the BPI-M3 from having, e.g., USB working to USB >> not working. -r323641 removed AWUSBPHY_TYPE_A83T >> from enum awusbphy_type because of what was missing >> from upstream DTS materials and such. >=20 > Uses of upstream DTS is active since ~2 years ago. > I think I removed support for USB on A83T because I couldn't test, but > maybe the code just work and adding the compatible string again might > do it. Feel free to send a patch on phabricator if it does. I last updated the BPI-M3's FreeBSD to be at head -r317015, so, a 2017-Apr-16 vintage, predating INO64 and the like if I remember right. It was working fine at the time and still boots with the root file system on an external USB SSD. Other than a "Cleanup BROKEN/IGNORE for 10.3" sysutils/u-boot-sinovoip-bpi-m3 still goes back to -r419007 (2016-Jul-24). The distinfo goes back to -r418429 (2016-Jul-12). These predate the -r424735 (2016-Oct-26) creation of sysutils/u-boot-master . That means that head -r317015 was compatible with the active sysutils/u-boot-sinovoip-bpi-m3 . The ubldr and ubldr.bin in use on the BPI-M3 that I have access to shows: -rwxr-xr-x 1 root wheel 271949 Oct 24 03:28:54 2016 ubldr -rwxr-xr-x 1 root wheel 224044 Oct 24 03:28:54 2016 ubldr.bin and so should match sysutils/u-boot-sinovoip-bpi-m3 and I should not have to update. My memory is that sinovoip-bpi-m3 has .dt* files that include each other in an unusual manor that can lead to misinterpretation if one assumes the usual structure for what files to look at. For example, the USB material can be missed. I'll see about looking at base/head differences (such as -r323641) and see if I can guess well at what things should be (in case there is anything else). But for me it will be guesswork and may take some time as I explore unfamiliar material. I'll let you know when I get that far. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 21 23:09:50 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 6CC34E3C84C for ; Sat, 21 Oct 2017 23:09:50 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A2ED6EC56 for ; Sat, 21 Oct 2017 23:09:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 21013 invoked from network); 21 Oct 2017 23:09:47 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 21 Oct 2017 23:09:47 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 21 Oct 2017 19:09:47 -0400 (EDT) Received: (qmail 28822 invoked from network); 21 Oct 2017 23:09:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Oct 2017 23:09:47 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id E3BE5EC8F7A; Sat, 21 Oct 2017 16:09:46 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r324822 - head/sys/modules/dtb/allwinner [removal of sinovoip-bpi-m3.dts from sys/modules/dtb/allwinner/Makefile DTS list] Date: Sat, 21 Oct 2017 16:09:46 -0700 References: <3AD6B1F8-512C-43BB-AC76-7721454AD02F@dsl-only.net> <20171021195812.5bdb902401b8e756b6abfe40@bidouilliste.com> <20171021204356.47e3cd6066144bcd07f46699@bidouilliste.com> <50728566-11C2-45EB-8367-00CAF38D4548@dsl-only.net> To: Emmanuel Vadot , freebsd-arm In-Reply-To: <50728566-11C2-45EB-8367-00CAF38D4548@dsl-only.net> Message-Id: X-Mailer: Apple Mail (2.3273) 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: Sat, 21 Oct 2017 23:09:50 -0000 On 2017-Oct-21, at 2:06 PM, Mark Millard wrote: > On 2017-Oct-21, at 11:43 AM, Emmanuel Vadot = wrote: >=20 >> On Sat, 21 Oct 2017 11:26:57 -0700 >> Mark Millard wrote: >>=20 >>> On 2017-Oct-21, at 10:58 AM, Emmanuel Vadot wrote: >>>=20 >>>>>> . . . >>>=20 >>> If I understand the current status correctly, the >>> recent changes to use upstream DTS materials took >>> the BPI-M3 from having, e.g., USB working to USB >>> not working. -r323641 removed AWUSBPHY_TYPE_A83T >>> from enum awusbphy_type because of what was missing >>> from upstream DTS materials and such. >>=20 >> Uses of upstream DTS is active since ~2 years ago. >> I think I removed support for USB on A83T because I couldn't test, = but >> maybe the code just work and adding the compatible string again might >> do it. Feel free to send a patch on phabricator if it does. >=20 > . . . Note: My "normal" environment (such as /usr/src/ ) is currently at head -r324743 . That is what I'm comparing -r317015 to for now. I've started by seeing what if anything changed in .dt* files. Unfortunately I ran into changes in .dt* files used for bpi-m3 since -r317015 (indirect via #includes). At issue are at least: #include "sunxi-common-regulators.dtsi" and #include "sun8i-a83t.dtsi" (but the last one is complicated by multiple files with that name in different places, one having updates and the other not). It looks like I'll need a hint if any of the .dt* file that I've found so far that have differences since -r317015 have implications about the sysutils/u-boot-sinovoip-bpi-m3 being sufficient or not (for example). There might be implications for kernel versions as well. It might be that to have things work would require substituting the old content into the bpi-m3 specific files instead of including modern. I'm not so sure anyone that works on the code regularly would want such a thing: They might prefer that support be dropped for BPI-M3, including removal of: sysutils/u-boot-sinovoip-bpi-m3 More detail if needed. . . While: sys/boot/fdt/dts/arm/ does not have differences that I've found for bpi-m3 or a83t some gnu/dts/arm/ material that is included does: #include "sunxi-common-regulators.dtsi" The included file was updated in -r32130 , -r320834 , and -r324820 (today). The following may have differences in the included file: #include "sun8i-a83t.dtsi" Why "may"? # find /usr/src/sys/ -name sun8i-a83t.dtsi -print /usr/src/sys/boot/fdt/dts/arm/sun8i-a83t.dtsi /usr/src/sys/gnu/dts/arm/sun8i-a83t.dtsi There are two files with the matching name that might be found. I've not figured out which is used yet. The boot/fdt one is unchanged from -r299748 (2016-May-14 when it was created) but the gnu one has been updated in -r32130 , -r320834 , and -r324820 (today), much like for sunxi-common-regulators.dtsi . (I might not have traced every include that has potential updates but the above ones probably give a big hint at compatibility implications for someone that knows what they are looking at.) =3D=3D=3D Mark Millard markmi at dsl-only.net