From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) by mx.groups.io with SMTP id smtpd.web12.1134.1611991778027623350 for ; Fri, 29 Jan 2021 23:29:38 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@assonance-org.20150623.gappssmtp.com header.s=20150623 header.b=PF300AlZ; spf=pass (domain: assonance.org, ip: 209.85.167.177, mailfrom: aaron@assonance.org) Received: by mail-oi1-f177.google.com with SMTP id g69so12595686oib.12 for ; Fri, 29 Jan 2021 23:29:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=assonance-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PYclrDbE32XZp0dvJrEv/akBcmzOGZQgeylaBEkt164=; b=PF300AlZVsX/HJWM0DSIILeNtnn9eYDXg4lpZV+1TxvHeVsZ6XD40PzvfypNHfTAiV 04gMppbXDjk4V0/UPpFGMcgY+go65Y/dxu/NJHNfW0KrhR+33icRT0+bj2pbSrYTO1c9 YNbzxRHXBCAIN4xAbEj1FkssaF17AJ0B/ZkuFsUZabq50ePFWnOaPv7sZubCqZiz5ZGJ Y5Bflm7f637MT/bH8AgbGZxdUaKsLAcCI0LHSxx3hnwkHrwe9vA251M9W4RON1daetMQ 3ar7pkXag1bmMz4VXpBs145EUZ41e03P9pzWFC+H7vk2rK9cHfQ+ckpuEj17t1Ax70OJ gfGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PYclrDbE32XZp0dvJrEv/akBcmzOGZQgeylaBEkt164=; b=Mb9K3tljvnq80dAi7Saoj8BVjjhvSgg/jeCAJjAHzLHh8GgNSQpQjv9PfZRpybuneQ DGKKbd3VU16O7Ml3he2o4v50909d132wNmyRzJSp5C4xZOtJ0vDE9zCmavgeZfaO4wY/ 8+qGsOR3sbL5g089wTg1Oh3bxLq9MflnYB2D2co4HLZkVVYlOUifnGvZPRqOvmvr6AxY HWQm0BHpXO+JpEzBTPh2R2stmb6YV1o27ZKDcnpKM6kjQ3YdhhuIFQFd9DXhfa4ClL4B 6ZfzTenxMuZ7+IdIvxpIeI8/8pZKnFLKLMOII38uKTArV88jZgXpigickuFaQvwBC8e4 1Lfw== X-Gm-Message-State: AOAM531wl55RY5xkducvmaZ+RMt1DLF18jhYFx4BnKgeNVG50RuARITe 4PTPXAWQP8OpSoCJwU9RZ9F3f4dsN0T90OHcqAhzRw== X-Google-Smtp-Source: ABdhPJyB+KJbYM0NQzac8qqpaib8JQqZOFRSz4CIwnTv+0ftrYTyBj2TsSdvhzLpAy/raktYtOFReUYTHMbIQ/Uray0= X-Received: by 2002:aca:b9c1:: with SMTP id j184mr5010013oif.63.1611991777210; Fri, 29 Jan 2021 23:29:37 -0800 (PST) MIME-Version: 1.0 References: <165CDE54CF259D2E.7022@lists.yoctoproject.org> <165EF1C95601254E.16314@lists.yoctoproject.org> In-Reply-To: <165EF1C95601254E.16314@lists.yoctoproject.org> From: "Joel A Cohen" Date: Sat, 30 Jan 2021 02:29:26 -0500 Message-ID: Subject: Re: [yocto] Writing a BSP from downstream kernel sources To: Aaron Cohen Cc: Jonas Vautherin , Diego Santa Cruz , Paul Barker , Yocto-mailing-list Content-Type: multipart/alternative; boundary="00000000000043035305ba1915e6" --00000000000043035305ba1915e6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Actually, I found the upstream patch I backported, which you're probably better off using (same diff though). https://lore.kernel.org/patchwork/patch/773330/ On Sat, Jan 30, 2021 at 2:26 AM Joel A Cohen via lists.yoctoproject.org wrote: > I'm not sure if this is your issue, but I had a similar issue ilog2 and > the disassembler and fixed it by backporting this patch. > > No guarantees, but perhaps it will help. > > --Aaron > > > On Fri, Jan 29, 2021 at 9:51 PM Jonas Vautherin > wrote: > >> Thanks a lot for the advice! However, I can't seem to find a `const` th= at >> I can simply remove. To give more context, here is the log output aroun= d >> such an error (it seems like it is often surrounded by this log2.h warn= ing, >> by the way): >> >> | In file included from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/kernel.h:11, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/kallsyms.h:9, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/ftrace.h:10, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/kernel/extable.c:18: >>> | >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/log2.h:22:1: >>> warning: ignoring attribute 'noreturn' because it conflicts with attri= bute >>> 'const' [-Wattributes] >>> | 22 | int ____ilog2_NaN(void); >>> | | ^~~ >>> | CC fs/fat/dir.o >>> | In file included from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/kernel.h:11, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/list.h:8, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/module.h:9, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/fs/fat/dir.c:16: >>> | >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/log2.h:22:1: >>> warning: ignoring attribute 'noreturn' because it conflicts with attri= bute >>> 'const' [-Wattributes] >>> | 22 | int ____ilog2_NaN(void); >>> | | ^~~ >>> | CC block/deadline-iosched.o >>> | In file included from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/kernel.h:11, >>> | from >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/block/deadline-iosched.c:6: >>> | >>> /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/= kernel-source/include/linux/log2.h:22:1: >>> warning: ignoring attribute 'noreturn' because it conflicts with attri= bute >>> 'const' [-Wattributes] >>> | 22 | int ____ilog2_NaN(void); >>> | | ^~~ >>> | /tmp/cc52vFrQ.s: Assembler messages: >>> | /tmp/cc52vFrQ.s:2683: Error: .err encountered >>> | /tmp/cc52vFrQ.s:2927: Error: .err encountered >>> | LD sound/sparc/built-in.o >>> | LD sound/spi/built-in.o >>> | make[3]: *** >>> [/home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroller3= /kernel-source/scripts/Makefile.build:257: >>> block/scsi_ioctl.o] Error 1 >>> >> >> I pasted the full output here, if that can help: >> https://paste.ubuntu.com/p/KqN8nVWmvv/. The lines that seem to get the >> log2 warning are: >> >> ``` >> extern __attribute__((const, noreturn)) >> int ____ilog2_NaN(void); >> ``` >> >> So there is a const there, but well... not sure what to do with it :-). >> >> Best, >> >> On Mon, Jan 25, 2021 at 9:00 AM Diego Santa Cruz < >> Diego.SantaCruz@spinetix.com> wrote: >> >>> *From:* yocto@lists.yoctoproject.org *O= n >>> Behalf Of *Jonas Vautherin via lists.yoctoproject.org >>> *Sent:* 24 January 2021 14:30 >>> *To:* Jonas Vautherin >>> *Cc:* Paul Barker ; Yocto-mailing-list < >>> yocto@lists.yoctoproject.org> >>> *Subject:* Re: [yocto] Writing a BSP from downstream kernel sources >>> >>> >>> >>> Just to close this: it seems like the gcc-cross-arm used by yocto >>> gatesgarth is too new for that specific downstream kernel (3.18.31). >>> >>> >>> >>> The goal was to get a proper BSP package for this device for a modern >>> yocto, so I don't think I will try with an older version of Yocto. If = I >>> compile an old gcc as part of a custom Yocto layer (on gatesgarth), I = am >>> guessing that I will have issues creating a distro that runs both on R= Pi >>> and on that older device (because RPi will have a newer kernel and gcc= , and >>> the skycontroller will use older ones). I also guess that the downstre= am >>> dts won't work with a modern kernel, and I would not know how to write= one >>> myself for that apq8009 chip. >>> >>> >>> >>> Hence, I'm giving up. Thanks a lot for the help :-). >>> >>> *[Diego Santa Cruz] Wait! **You may be able to get it working, see >>> below.* >>> >>> >>> >>> On Sat, Jan 23, 2021 at 2:07 PM Jonas Vautherin via >>> lists.yoctoproject.org >>> wrote: >>> >>> Thanks a lot for the answer! >>> >>> >>> >>> It seems like using `KCONFIG_MODE =3D "--alldefconfig"` with >>> `KBUILD_DEFCONFIG =3D "msm8909_defconfig"` now ends up with the same k= ind of >>> errors as when I use the defconfig from the downstream kernel [1], i.e= .: >>> >>> >>> >>> *[Diego Santa Cruz] I happen to be doing a similar kind of work, getti= ng >>> an even older (2.6.37+) downstream kernel for an ARM machine to compil= e >>> with recent GCC in Yocto, in my case GCC 9.3 from dunfell. There are a= few >>> fixes and backports necessary to make it happen and boot. I=E2=80=99m = not done with >>> the work yet, so I do not know how stable it is, but I have it booting= .* >>> >>> ``` >>> >>> | /tmp/ccz8jKgm.s: Assembler messages: >>> | /tmp/ccz8jKgm.s:985: Error: .err encountered >>> >>> ``` >>> >>> *[Diego Santa Cruz] The fix here is rather simple once you understand >>> what=E2=80=99s going on, the problem is abusive use of const for regis= ter >>> variables, see >>> https://gcc.gnu.org/onlinedocs/gcc-9.3.0/gcc/Local-Register-Variables.= html >>> >>> so when put_user() is used for a literal constant value it gets assign= ed >>> the wrong register, so just remove the const qualifier from the put_us= er() >>> register variable assignment for the value argument. For my older kern= el >>> the patch is like this.* >>> >>> --- arch/arm/include/asm/uaccess.h >>> >>> +++ arch/arm/include/asm/uaccess.h >>> >>> @@ -145,7 +145,7 @@ >>> >>> #define >>> put_user(x,p) >>> \ >>> >>> >>> ({ >>> \ >>> >>> - register const typeof(*(p)) __r2 >>> asm("r2") =3D (x); \ >>> >>> + register typeof(*(p)) __r2 asm("r2") = =3D >>> (x); \ >>> >>> register const typeof(*(p)) __user *__= p >>> asm("r0") =3D (p);\ >>> >>> register int __e >>> asm("r0"); \ >>> >>> switch (sizeof(*(__p))) >>> { \ >>> >>> >>> >>> Could it be related to the tuning, e.g. I'm somehow defining a wrong >>> toolchain in my machine configuration [2] and it fails to build? I was >>> thinking about the tune-cortexa7.inc include, though it seems to me th= at >>> the apq8009 is a cortexa7 [3]: >>> >>> >>> >>> *[Diego Santa Cruz] Other commits from post 3.18 that you may need to >>> backport are the following (start from bottom of list) * >>> >>> 474c90156c8dcc2fa815e6716cc9394d7930cb9c give up on gcc ilog2() consta= nt >>> optimizations >>> >>> cb984d101b30eb7478d32df56a0023e4603cba7f compiler-gcc: integrate the >>> various compiler-gcc[345].h files >>> >>> f6d133f877c8bb0a0934dc8c521c758ee771e901 compiler-gcc.h: neatening >>> >>> 7829fb09a2b4268b30dd9bc782fa5ebee278b137 lib: make memzero_explicit mo= re >>> robust against dead store elimination >>> >>> cb4188ac8e5779f66b9f55888ac2c75b391cde44 compiler: introduce >>> __alias(symbol) shortcut >>> >>> 0b053c9518292705736329a8fe20ef4686ffc8e9 lib: memzero_explicit: use >>> barrier instead of OPTIMIZER_HIDE_VAR >>> >>> ee91ef6173e81819f5ff610c2485802081635657 bufferhead: force inlining of >>> buffer head flag operations >>> >>> cc7fce80229067890365c1ee196be5d304d36dea mtd: blkdevs: fix switch-bool >>> compilation warning >>> >>> >>> >>> >>> >>> > The Qualcomm Snapdragon 212 APQ8009 is an entry level SoC for Androi= d >>> based tablets and smartphones. It contains four ARM Cortex-A7 CPU core= s >>> (quad core) >>> >>> >>> >>> [1]: >>> https://github.com/parrot-opensource/skycontroller3-opensource/blob/ma= ster/sources/linux-3.18.31/linux.config >>> >>> [2]: >>> https://github.com/JonasVautherin/meta-skycontroller3/blob/main/conf/m= achine/skycontroller3.conf#L32 >>> >>> [3]: >>> https://www.notebookcheck.net/Qualcomm-Snapdragon-212-APQ8009-SoC-Benc= hmarks-and-Specs.169859.0.html >>> >>> >>> >>> Best, >>> >>> >>> >>> On Sat, Jan 23, 2021 at 11:06 AM Paul Barker >>> wrote: >>> >>> On Sat, 23 Jan 2021 at 02:29, Jonas Vautherin >>> wrote: >>> > >>> > As a learning experience, I am trying to create a BSP for a device I >>> own and whose downstream kernel is published. The device in question i= s the >>> Parrot Skycontroller3, and the sources are available here. >>> > >>> > Let me start by sharing my issue. When I build the kernel with >>> `bitbake virtual/kernel`, it fails with errors like: >>> > >>> > ``` >>> > | AS arch/arm/lib/backtrace.o >>> > | AS arch/arm/lib/bswapsdi2.o >>> > | AS arch/arm/lib/call_with_stack.o >>> > | /tmp/ccz8jKgm.s: Assembler messages: >>> > | /tmp/ccz8jKgm.s:985: Error: .err encountered >>> > | /tmp/ccz8jKgm.s:1033: Error: .err encountered >>> > | /tmp/ccz8jKgm.s:6812: Error: .err encountered >>> > ``` >>> > >>> > My layer is available here. >>> > >>> > I created it getting inspiration from meta-raspberrypi and >>> meta-qti-bsp, which seems to have the same CPU: apq8009. According to = the >>> Parrot sources, my device runs a Qualcomm apq8009/msm89090 cpu. In my = repo, >>> I use as a defconfig file the linux.config that is available in the Pa= rrot >>> sources (I copied it in my kernel recipe under `files/defconfig` and a= dded >>> it to SRC_URI). >>> > >>> > The Parrot sources also refer to `LINUX_DEFAULT_CONFIG_TARGET :=3D >>> msm8909_defconfig`, so I tried to set `KBUILD_DEFCONFIG =3D >>> "msm8909_defconfig"`, but that is failing with different errors, such = as: >>> > >>> > ``` >>> > error: 'VM_ARM_DMA_CONSISTENT' undeclared (first use in this >>> function); did you mean 'DMA_ATTR_NON_CONSISTENT'? >>> > ``` >>> > >>> > or >>> > >>> > ``` >>> > error: 'L_PTE_YOUNG' undeclared >>> > ``` >>> > >>> > As a side note, their `drivers/Kconfig` seemed invalid, so I patched >>> it. >>> > >>> > I am a bit lost now, not completely sure where my issues come from. = I >>> realize that changing the defconfig has quite some impact (I get diffe= rent >>> errors), and also that my machine configuration may be completely wron= g (I >>> am essentially guessing from the fact that it is an apq8009/msm8909, b= ut >>> for instance the tuning I just copied from meta-qti-bsp, which may be >>> invalid). >>> > >>> > I would be glad if I could get hints about debugging this. Again, it >>> is really a learning project: I would like to learn how to create a BS= P >>> from a downstream kernel. >>> >>> I think setting `KBUILD_DEFCONFIG =3D "msm8909_defconfig"` is likely t= he >>> correct approach here. What you may be missing though is the correct >>> value for KCONFIG_MODE. By default, the supplied defconfig file is >>> copied to .config but dependencies between config options aren't >>> resolved. You need to set `KCONFIG_MODE =3D "--alldefconfig"` to get t= he >>> equivalent of `make msm8909_defconfig` to occur. See >>> >>> https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-kerne= l/linux/linux-raspberrypi.inc#L19 >>> for an idea of how this is done for Raspberry Pi. >>> >>> Thanks, >>> >>> -- >>> Paul Barker >>> Konsulko Group >>> >>> >>> -- >>> >>> *Diego Santa Cruz, PhD *Technology Architect >>> spinetix.com >>> >> >> >> >> >=20 > > --00000000000043035305ba1915e6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Actually, I found the upstream patch I backported, wh= ich you're probably better off using (same diff though).

=

On Sat, Jan 30, 202= 1 at 2:26 AM Joel A Cohen via lis= ts.yoctoproject.org <aaron=3Dassonance.org@lists.yoctoproject.org> wrote:
= I'm not sure if this is your issue, but I had a similar issue ilog2 and= the disassembler and fixed it by backporting this patch.

No guarantees, but perhaps it will help.

-= -Aaron


On Fri, Jan 29, 2021 at 9:51 PM Jonas Vauthe= rin <jona= s.vautherin@gmail.com> wrote:
Thanks a lot for the advice! However,= I can't seem to find a `const` that I can simply remove. To give more = context, here is the log output around such an error (it seems like it is o= ften surrounded by this log2.h warning, by the way):

| In file included from /home/jon= es/Documents/yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/= include/linux/kernel.h:11,
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0from /home/jones/Documents/yocto/poky/build/tmp/work-s= hared/skycontroller3/kernel-source/include/linux/kallsyms.h:9,
| =C2=A0 = = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0from /home/jones/Do= cuments/yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/inclu= de/linux/ftrace.h:10,
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0from /home/jones/Documents/yocto/poky/build/tmp/work-shared/s= kycontroller3/kernel-source/kernel/extable.c:18:
| /home/jones/Documents= /yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/include/linu= x/log2.h:22:1: warning: ignoring attribute 'noreturn' because it co= nflicts with attribute 'const' [-Wattributes]
| =C2=A0 =C2=A022 = | int ____ilog2_NaN(void);
| =C2=A0 =C2=A0 =C2=A0 | ^~~
| =C2=A0 CC = =C2=A0 =C2=A0 =C2=A0fs/fat/dir.o
| In file included from /home/jones/Do= cuments/yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/inclu= de/linux/kernel.h:11,
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0from /home/jones/Documents/yocto/poky/build/tmp/work-shared/s= kycontroller3/kernel-source/include/linux/list.h:8,
| =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0from /home/jones/Documents/yo= cto/poky/build/tmp/work-shared/skycontroller3/kernel-source/include/linux/m= odule.h:9,
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= = =A0from /home/jones/Documents/yocto/poky/build/tmp/work-shared/skycontroll= er3/kernel-source/fs/fat/dir.c:16:
| /home/jones/Documents/yocto/poky/bu= ild/tmp/work-shared/skycontroller3/kernel-source/include/linux/log2.h:22:1:= warning: ignoring attribute 'noreturn' because it conflicts with a= ttribute 'const' [-Wattributes]
| =C2=A0 =C2=A022 | int ____ilog= 2_NaN(void);
| =C2=A0 =C2=A0 =C2=A0 | ^~~
| =C2=A0 CC =C2=A0 =C2=A0 = =C2=A0block/deadline-iosched.o
| In file included from /home/jones/Docu= ments/yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/include= /linux/kernel.h:11,
| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0from /home/jones/Documents/yocto/poky/build/tmp/work-shared/s= kycontroller3/kernel-source/block/deadline-iosched.c:6:
| /home/jones/Do= cuments/yocto/poky/build/tmp/work-shared/skycontroller3/kernel-source/inclu= de/linux/log2.h:22:1: warning: ignoring attribute 'noreturn' becaus= e it conflicts with attribute 'const' [-Wattributes]
| =C2=A0 = =C2=A022 | int ____ilog2_NaN(void);
| =C2=A0 =C2=A0 =C2=A0 | ^~~
| /= tmp/cc52vFrQ.s: Assembler messages:
| /tmp/cc52vFrQ.s:2683: Error: .err = encountered
| /tmp/cc52vFrQ.s:2927: Error: .err encountered
| =C2=A0 = LD =C2=A0 =C2=A0 =C2=A0sound/sparc/built-in.o
| =C2=A0 LD =C2=A0 =C2=A0 = = =C2=A0sound/spi/built-in.o
| make[3]: *** [/home/jones/Documents/yocto/= poky/build/tmp/work-shared/skycontroller3/kernel-source/scripts/Makefile.bu= ild:257: block/scsi_ioctl.o] Error 1

I = pasted the full output here, if that can help:=C2=A0https://paste.ubuntu.com/p/Kq= N8nVWmvv/. The lines that seem to get the log2 warning are:
<= br>
```
extern __attribute__((const, noreturn))
in= t ____ilog2_NaN(void);
=C2=A0```

So there = is a const there, but well... not sure what to do with it :-).
Best,

On Mon, Jan 25, 2021 at 9:00 AM Diego Santa Cruz &l= t;Diego.S= antaCruz@spinetix.com> wrote:
From: yocto@lists.yoctoproject.org <yocto@lists.yoctopr= oject.org> On Behalf Of Jonas Vautherin via lists.yoctoproject.org
Sent: 24 January 2021 14:30
To: Jonas Vautherin <jonas.vautherin@gmail.com>
Cc: Paul Barker <pbarker@konsulko.com>; Yocto-mailing-list <yocto@lists.yoc= toproject.org>
Subject: Re: [yocto] Writing a BSP from downstream kernel sources

=C2=A0

Just to close this: it seems like the gcc-cross-arm= used by yocto gatesgarth is too new for that specific downstream kernel (3= .18.31).

=C2=A0

The goal was to get a proper BSP package for this d= evice for a modern yocto, so I don't think I will try with an older ver= sion of Yocto. If I compile an old gcc as part of a custom Yocto layer (on = gatesgarth), I am guessing that I will have issues creating a distro that runs both on RPi and on that older dev= ice (because RPi will have a newer kernel and gcc, and the skycontroller wi= ll use older ones). I also guess that the downstream dts won't work wit= h a modern kernel, and I would not know how to write one myself for that apq8009 chip.

=C2=A0

Hence, I'm giving up. Thanks a lot for the help= :-).

[Diego Santa Cruz] Wait! You may be able to get it working, see below.=

=C2=A0

On Sat, Jan 23, 2021 at 2:07 PM Jonas Vautherin via= lists.yoctoproject.org <jonas.vautherin=3Dgmail.com@lists.yoctoproject.o= rg> wrote:

Thanks a lot for the answer!

=C2=A0

It seems like using `KCONFIG_MODE =3D "--allde= fconfig"` with `KBUILD_DEFCONFIG =3D "msm8909_defconfig"` no= w ends up with the same kind of errors as when I use the defconfig from the= downstream kernel [1], i.e.:

=C2=A0

[Diego Santa Cruz] I happen to be doing a sim= ilar kind of work, getting an even older (2.6.37+) downstream kernel for an= ARM machine to compile with recent GCC in Yocto, in my case GCC 9.3 from d= unfell. There are a few fixes and backports necessary to make it happen and boot. I=E2=80=99m not done with the work = yet, so I do not know how stable it is, but I have it booting.

```

| /tmp/ccz8jKgm.s: Assembler messages:
| /tmp/ccz8jKgm.s:985: Error: .err encountered

```

[Diego Santa Cruz] The fix here is rather sim= ple once you understand what=E2=80=99s going on, the problem is abusive use= of const for register variables, see https://gcc.gnu.org/onlinedocs/gcc-9.3.0/gcc/Local-Register-Variables.html= so when put_user() is used for a literal constant value it gets assign= ed the wrong register, so just remove the const qualifier from the put_user= () register variable assignment for the value argument. For my older kernel the patch is like this.=

--- arch/arm/include/a= sm/uaccess.h

+++ arch/arm/include/a= sm/uaccess.h

@@ -145,7 +145,7 @@=

=C2=A0#define put_user= (x,p)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 \

=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ({= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 \

-=C2=A0=C2=A0=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 register const typeof(*(p)) __r2 asm("r2") =3D (= x); \

+=C2=A0=C2=A0=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 register typeof(*(p)) __r2 asm("r2") =3D (x);=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 \

=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 register const typeof(*(p)) __user *__p asm("r0= ") =3D (p);\

=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 register int __e asm("r0");=C2=A0=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 \

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 switch (sizeof(*(__p))) {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= = =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 \

=C2=A0

Could it be related to the tuning, e.g. I'm som= ehow defining a wrong toolchain in my machine configuration [2] and it fail= s to build? I was thinking about the tune-cortexa7.inc include, though it s= eems to me that the apq8009 is a cortexa7 [3]:

=C2=A0

[Diego Santa Cruz] Other commits from post 3.= 18 that you may need to backport are the following (start from bottom of li= st)

474c90156c8dcc2fa815e6716cc9394d7930cb9c give up on= gcc ilog2() constant optimizations

cb984d101b30eb7478d32df56a0023e4603cba7f compiler-g= cc: integrate the various compiler-gcc[345].h files

f6d133f877c8bb0a0934dc8c521c758ee771e901 compiler-g= cc.h: neatening

7829fb09a2b4268b30dd9bc782fa5ebee278b137 lib: make = memzero_explicit more robust against dead store elimination

cb4188ac8e5779f66b9f55888ac2c75b391cde44 compiler: = introduce __alias(symbol) shortcut

0b053c9518292705736329a8fe20ef4686ffc8e9 lib: memze= ro_explicit: use barrier instead of OPTIMIZER_HIDE_VAR

ee91ef6173e81819f5ff610c2485802081635657 bufferhead= : force inlining of buffer head flag operations

cc7fce80229067890365c1ee196be5d304d36dea mtd: blkde= vs: fix switch-bool compilation warning

=C2=A0

=C2=A0

>=C2=A0The Qualcomm Snapdragon 212 APQ8009 is an= entry level SoC for Android based tablets and smartphones. It contains fou= r ARM Cortex-A7 CPU cores (quad core)

=C2=A0

=C2=A0

Best,

=C2=A0

On Sat, Jan 23, 2021 at 11:06 AM Paul Barker <pbarker@konsulko.co= m> wrote:

On Sat, 23 Jan 2021 at 02:29, Jonas Vautherin <<= a href=3D"mailto:jonas.vautherin@gmail.com" target=3D"_blank">jonas.vauther= in@gmail.com> wrote:
>
> As a learning experience, I am trying to create a BSP for a device I = own and whose downstream kernel is published. The device in question is the= Parrot Skycontroller3, and the sources are available here.
>
> Let me start by sharing my issue. When I build the kernel with `bitba= ke virtual/kernel`, it fails with errors like:
>
> ```
> |=C2=A0 =C2=A0AS=C2=A0 =C2=A0 =C2=A0 arch/arm/lib/backtrace.o
> |=C2=A0 =C2=A0AS=C2=A0 =C2=A0 =C2=A0 arch/arm/lib/bswapsdi2.o
> |=C2=A0 =C2=A0AS=C2=A0 =C2=A0 =C2=A0 arch/arm/lib/call_with_stack.o > | /tmp/ccz8jKgm.s: Assembler messages:
> | /tmp/ccz8jKgm.s:985: Error: .err encountered
> | /tmp/ccz8jKgm.s:1033: Error: .err encountered
> | /tmp/ccz8jKgm.s:6812: Error: .err encountered
> ```
>
> My layer is available here.
>
> I created it getting inspiration from meta-raspberrypi and meta-qti-b= sp, which seems to have the same CPU: apq8009. According to the Parrot sour= ces, my device runs a Qualcomm apq8009/msm89090 cpu. In my repo, I use as a= defconfig file the linux.config that is available in the Parrot sources (I copied it in my kernel recipe under= `files/defconfig` and added it to SRC_URI).
>
> The Parrot sources also refer to `LINUX_DEFAULT_CONFIG_TARGET :=3D ms= m8909_defconfig`, so I tried to set `KBUILD_DEFCONFIG =3D "msm8909_def= config"`, but that is failing with different errors, such as:
>
> ```
> error: 'VM_ARM_DMA_CONSISTENT' undeclared (first use in this = function); did you mean 'DMA_ATTR_NON_CONSISTENT'?
> ```
>
> or
>
> ```
> error: 'L_PTE_YOUNG' undeclared
> ```
>
> As a side note, their `drivers/Kconfig` seemed invalid, so I patched = it.
>
> I am a bit lost now, not completely sure where my issues come from. I= realize that changing the defconfig has quite some impact (I get different= errors), and also that my machine configuration may be completely wrong (I= am essentially guessing from the fact that it is an apq8009/msm8909, but for instance the tuning I just copied = from meta-qti-bsp, which may be invalid).
>
> I would be glad if I could get hints about debugging this. Again, it = is really a learning project: I would like to learn how to create a BSP fro= m a downstream kernel.

I think setting `KBUILD_DEFCONFIG =3D "msm8909_defconfig"` is li= kely the
correct approach here. What you may be missing though is the correct
value for KCONFIG_MODE. By default, the supplied defconfig file is
copied to .config but dependencies between config options aren't
resolved. You need to set `KCONFIG_MODE =3D "--alldefconfig"` to= get the
equivalent of `make msm8909_defconfig` to occur. See
https://github.= com/agherzan/meta-raspberrypi/blob/master/recipes-kernel/linux/linux-raspbe= rrypi.inc#L19
for an idea of how this is done for Raspberry Pi.

Thanks,

--
Paul Barker
Konsulko Group


--
Diego Santa Cruz, PhD
Technology Architect
spinetix.com<= /span>







--00000000000043035305ba1915e6--