[android-building] Re: Touchscreen not working after building and flashing clean msm kernel for the Google Pixel blueline
On Friday, March 29, 2019 at 7:56:25 PM UTC+5:30, chiang...@gmail.com wrote: > > Hi > I have a doubt. If i compile kernel with gcc. It boots up but touch screen > is not working can I use AOSP gcc compiled modules.? > will it work? > I have built and flashed clean AOSP. > fastboot flashall -w > Which worked like a charm. > > Thn I build msm and flashed it with > fastboot boot Image.lz4-dtb > > The phone reboots. But then I am not able to use the touch screen at all. > I cant unlock the phones sim card. If I hold down the power button for a > while and reboot it. The touch screen works. Not sure what causes that, but > maybe the kernel has been removed and switched out with the old one? > > Another similar question is. If Id like to put the Image.lz4-dtb file > inside the AOSP ROM. Where should I put it, and is that possible? If that > would make me able to flash both kernel and ROM at the same time? > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/e5467601-f088-40fd-940f-8ab82bd1d565%40googlegroups.com.
Re: [android-building] Flashing kernel in pixel 2 (walleye)..?
yeah I read that but when I use envsetup.sh it show the output like below. = build config: /home/saurabh/walleyeMool/build.config ARCH=arm64 BRANCH=android-msm-wahoo-4.4 CC=clang CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-android- CROSS_COMPILE_ARM32=arm-linux-androideabi- DEFCONFIG=wahoo_defconfig EXTRA_CMDS='' KERNEL_DIR=private/msm-google POST_DEFCONFIG_CMDS='check_defconfig' CLANG_PREBUILT_BIN=prebuilts-master/clang/host/linux-x86/clang-4053586/bin/ LINUX_GCC_CROSS_COMPILE_PREBUILTS_BIN=prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin LINUX_GCC_CROSS_COMPILE_ARM32_PREBUILTS_BIN=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4 DTC_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/dtc LIBUFDT_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/libufdt FILES=" arch/arm64/boot/dtbo.img arch/arm64/boot/Image.lz4-dtb vmlinux System.map " IN_KERNEL_MODULES=1 STOP_SHIP_TRACEPRINTK=1 UNSTRIPPED_MODULES=" wlan.ko " PATH=/home/saurabh/walleyeMool/prebuilts-master/misc/linux-x86/libufdt:/home/saurabh/walleyeMool/prebuilts-master/misc/linux-x86/dtc:/home/saurabh/walleyeMool/prebuilts-master/misc/linux-x86/lz4:/home/saurabh/walleyeMool/prebuilts-master/clang/host/linux-x86/clang-4053586/bin/:/home/saurabh/walleyeMool/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin:/home/saurabh/walleyeMool/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:/home/saurabh/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/path/to/dir:/home/saurabh/bin On Sat, Jul 20, 2019 at 12:01 AM 'Dan Willemsen' via Android Building < android-building@googlegroups.com> wrote: > Have you read https://source.android.com/setup/build/building-kernels? > > - Dan > > On Fri, Jul 19, 2019 at 11:25 AM Saurabh Sakhare > wrote: > >> Hello, I'm newbie in kernel development. I want to know where can I get >> pixel 2 kernel and Clang toolchain and commands. I've been trying to >> compile it from last few days from random sources of git and google source. >> I could not compile a kernel I'm facing problem like some parse file is >> missing and arm32 toolchain. Pixel 2 is 64 bit wahoo. board is walleye. i'm >> trying every possible way somewhere I'm missing please help me out here. >> >> >> >> Then I rooted my phone and got SYSTEM_LAST_BOOT_logs it attached with >> mail. >> >> -- >> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to android-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-building+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/android-building/2a095acf-f8af-4bfe-acfa-661d0d2d616f%40googlegroups.com >> <https://groups.google.com/d/msgid/android-building/2a095acf-f8af-4bfe-acfa-661d0d2d616f%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/android-building/CALQgHdkoLvNzA2UKfsOzjDCogOuHPNbLi_wRpyHhSoYF%2BZfb2A%40mail.gmail.com > <https://groups.google.com/d/msgid/android-building/CALQgHdkoLvNzA2UKfsOzjDCogOuHPNbLi_wRpyHhSoYF%2BZfb2A%40mail.gmail.com?utm_medium=email_source=footer> > . > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.co
[android-building] Flashing kernel in pixel 2 (walleye)..?
Hello, I'm newbie in kernel development. I want to know where can I get pixel 2 kernel and Clang toolchain and commands. I've been trying to compile it from last few days from random sources of git and google source. I could not compile a kernel I'm facing problem like some parse file is missing and arm32 toolchain. Pixel 2 is 64 bit wahoo. board is walleye. i'm trying every possible way somewhere I'm missing please help me out here. Then I rooted my phone and got SYSTEM_LAST_BOOT_logs it attached with mail. -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/2a095acf-f8af-4bfe-acfa-661d0d2d616f%40googlegroups.com. isPrevious: false Build: google/walleye/walleye:9/PQ2A.190305.002/5240760:user/release-keys Hardware: walleye Revision: MP1 Bootloader: mw8998-002.0075.02 Radio: g8998-00253-1811291732 Kernel: Linux version 4.4.155-g7c022c6 (android-build@abfarm900) (Android clang version 5.0.300080 (based on LLVM 5.0.300080)) #1 SMP PREEMPT Fri Jan 11 21:31:16 UTC 2019
Re: [android-building] Re: Flashing AOSP master on Pixel failed (Android Q)
I've added wrong vendor image by mistake and now it stucked in bootloader mode. Showing error slot unbootable I tried to put in recovery mode but showing same error. And even phone is not showing on $fastboot devices. I was trying to re-flash images but nothing is working. Saurabh Sakhare 8007157873 On Mon, Mar 25, 2019 at 8:52 PM andrew_esh wrote: > I would not expect the AOSP source code base to be fully runnable at this > stage. Anything on there is probably going to be previews of bits and > pieces of what will eventually become the full release. The only way to get > Android Q running on a device at this stage is to install one of the binary > preview blobs. I don't expect the full source for Q to drop until late > September. > > https://www.techradar.com/news/android-q > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] make kernel of wahoo
I don't know why but I started getting errors as below. CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK include/generated/bounds.h CHK include/generated/timeconst.h CHK include/generated/asm-offsets.h CALLscripts/checksyscalls.sh make[1]: 'include/generated/vdso-offsets.h' is up to date. make[1]: 'include/generated/vdso32-offsets.h' is up to date. CHK scripts/mod/devicetable-offsets.h DTC arch/arm64/boot/dts/htc/overlay-walleye-xa_xb_xc.dtbo Error: arch/arm64/boot/dts/htc/base-msm8998-camera-sensor-mtp.dtsi:14.1-5 syntax error FATAL ERROR: Unable to parse input tree scripts/Makefile.lib:308: recipe for target 'arch/arm64/boot/dts/htc/overlay-walleye-xa_xb_xc.dtbo' failed make[2]: *** [arch/arm64/boot/dts/htc/overlay-walleye-xa_xb_xc.dtbo] Error 1 scripts/Makefile.build:551: recipe for target 'arch/arm64/boot/dts/htc' failed make[1]: *** [arch/arm64/boot/dts/htc] Error 2 arch/arm64/Makefile:179: recipe for target 'dtbs' failed make: *** [dtbs] Error 2 Saurabh Sakhare 8007157873 On Mon, Mar 18, 2019 at 7:58 PM 'Alessio Balsini' via Android Building < android-building@googlegroups.com> wrote: > Hi, > > That is not the right procedure to build Wahoo kernels: as the > documentation says, that is an example for HiKey development boards. > Please have a look at our recently updated Building Kernels documentation, > which shows a much simpler out-of-the-box procedure to build custom > kernels: https://source.android.com/setup/build/building-kernels. > > Regards, > Alessio > > > On Sat, Mar 16, 2019 at 3:37 PM <927002...@qq.com> wrote: > >> *i put below:* >> export ARCH=arm64 >> export CROSS_COMPILE_ARM32=aarch64-linux-android- >> PATH=/home/shallin/android9_r22/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:$PATH >> make wahoo_defconfig *and then i put "make" ,show like this* >> >> [image: error.jpg] >> >> how can i do >> >> -- >> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to android-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-building+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] make kernel of wahoo
Check your build.config file in kernel. So it has what needed config directories and files. LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4 DTC_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/dtc LIBUFDT_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/libufdt Download this lz4(Compression algorithm),dtc(Device Tree compiler),libufdt(Used for optimization of dtos) and give proper path and config and use CC=clang. Coz pixel 2 user level programms are compiled using clang. So some of the files will be compile using Clang. export ARCH=arm64 export CROSS_COMPILE_ARM32=~/PATH_TO_directory(arm eabi 4.7 or 4.8)/arm-eabi- export CROSS_COMPILE=~/PATH_TO_DIR(aarch64)/ LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4 DTC_PREBUILTS_BIN=~/pATH TO/linux-x86/dtc LIBUFDT_PREBUILTS_BIN=`/pATH_TO_DIR/linux-x86/libufdt Saurabh Sakhare 8007157873 On Sat, Mar 16, 2019 at 9:07 PM <927002...@qq.com> wrote: > *i put below:* > export ARCH=arm64 > export CROSS_COMPILE_ARM32=aarch64-linux-android- > PATH=/home/shallin/android9_r22/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:$PATH > make wahoo_defconfig *and then i put "make" ,show like this* > > [image: error.jpg] > > how can i do > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Re: Unable to build bluecross kernel
No I wanted for pixel 2. It has wahoo board. so wahoo_defconfig works fine
for it's configuration.
Thanks Mate
Saurabh Sakhare
On Tue, Mar 12, 2019 at 12:05 AM 'Chris Fries' via Android Building <
android-building@googlegroups.com> wrote:
> The b1c1_defconfig should be the one you want for Pixel 3. Does that
> resolve the issue?
>
> -Chris
>
>
> On Monday, March 11, 2019 at 1:24:34 PM UTC-5, Saurabh Sakhare wrote:
>>
>> Use Makefile in KSRC to get to know more about kernel requirements and
>> compatibility. And check build.config file that'll give you specific
>> requirements for kernel compilation.
>> I'm compiling wahoo kernel so in my build.config i found
>> "ARCH=arm64
>> BRANCH=android-msm-wahoo-4.4
>> CC=clang
>> CLANG_TRIPLE=aarch64-linux-gnu-
>> CROSS_COMPILE=aarch64-linux-android-
>> CROSS_COMPILE_ARM32=arm-linux-androideabi-
>> DEFCONFIG=wahoo_defconfig
>> EXTRA_CMDS=''
>> KERNEL_DIR=private/msm-google
>> POST_DEFCONFIG_CMDS='check_defconfig'
>>
>> CLANG_PREBUILT_BIN=prebuilts-master/clang/host/linux-x86/clang-4053586/bin/
>>
>> LINUX_GCC_CROSS_COMPILE_PREBUILTS_BIN=prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
>>
>> LINUX_GCC_CROSS_COMPILE_ARM32_PREBUILTS_BIN=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin
>> LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4
>> DTC_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/dtc
>> LIBUFDT_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/libufdt"
>>
>> This info so I got all requirements to build the kerne. And do add path
>> properly check path using tab.
>>
>> Saurabh Sakhare
>>
>>
>>
>> On Mon, Mar 11, 2019 at 10:46 PM Emanuele Vannacci
>> wrote:
>>
>>> i have the same problem. Do you solve this error?
>>>
>>> Il giorno giovedì 15 novembre 2018 20:44:31 UTC+1, Lance Vick ha scritto:
>>>>
>>>> I am unable to build a kernel for crosshatch.
>>>>
>>>> Looks like a missing file or broken path?
>>>>
>>>> Also I am only assuming "android-msm-bluecross-4.9-pie-dr1-release" for
>>>> the branch and "sdm845-perf" for the defconfig from looking at git history
>>>> as there is no documentation for crosshatch or blueline in
>>>> https://source.android.com/setup/build/building-kernels
>>>>
>>>> Build commands:
>>>>
>>>> git clone https://android.googlesource.com/kernel/msm kernel/msm
>>>> cd "kernel/msm"
>>>> git checkout android-msm-bluecross-4.9-pie-dr1-release
>>>>
>>>> export ARCH=arm64
>>>> export
>>>> CROSS_COMPILE="$PWD/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-${gcc_version}/bin/aarch64-linux-android-"
>>>>
>>>> make "sdm845-perf_defconfig"
>>>> make -j8
>>>>
>>>>
>>>> Failure output:
>>>>
>>>> In file included from drivers/clk/qcom/mdss/mdss_pll_trace.h:116:0,
>>>>
>>>> from drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.c:24:
>>>>
>>>> ./include/trace/define_trace.h:88:43: fatal error: ./mdss_pll_trace.h:
>>>> No such file or directory
>>>> #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
>>>>
>>>> compilation terminated.
>>>>
>>>> scripts/Makefile.build:336: recipe for target
>>>> 'drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.o' failed
>>>> make[4]: *** [drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.o] Error 1
>>>> make[4]: *** Waiting for unfinished jobs
>>>> scripts/Makefile.build:650: recipe for target 'drivers/clk/qcom/mdss'
>>>> failed
>>>> make[3]: *** [drivers/clk/qcom/mdss] Error 2
>>>> scripts/Makefile.build:650: recipe for target 'drivers/clk/qcom' failed
>>>> make[2]: *** [drivers/clk/qcom] Error 2
>>>> scripts/Makefile.build:650: recipe for target 'drivers/clk' failed
>>>> make[1]: *** [drivers/clk] Error 2
>>>> make[1]: *** Waiting for unfinished jobs
>>>>
>>>> create image file: arch/arm64/boot/dtbo.img...
>>>> Can not read file:
>>>> arch/arm64/boot/dts/google/sdm845-v2-b1c1-devboard.dtbo
>>>> arch/arm64/boot/Makefile:71: recipe for target
>>>> 'arch/arm64/boot/dtbo.img' failed
>>>> make[1]: *** [arch/arm64/boot/dtbo.img] Error 255
>>>> arch/arm64/Makefile:214: recipe for target 'dtbo.img' failed
>>>> mak
Re: [android-building] Re: Unable to build bluecross kernel
Use Makefile in KSRC to get to know more about kernel requirements and
compatibility. And check build.config file that'll give you specific
requirements for kernel compilation.
I'm compiling wahoo kernel so in my build.config i found
"ARCH=arm64
BRANCH=android-msm-wahoo-4.4
CC=clang
CLANG_TRIPLE=aarch64-linux-gnu-
CROSS_COMPILE=aarch64-linux-android-
CROSS_COMPILE_ARM32=arm-linux-androideabi-
DEFCONFIG=wahoo_defconfig
EXTRA_CMDS=''
KERNEL_DIR=private/msm-google
POST_DEFCONFIG_CMDS='check_defconfig'
CLANG_PREBUILT_BIN=prebuilts-master/clang/host/linux-x86/clang-4053586/bin/
LINUX_GCC_CROSS_COMPILE_PREBUILTS_BIN=prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
LINUX_GCC_CROSS_COMPILE_ARM32_PREBUILTS_BIN=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin
LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4
DTC_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/dtc
LIBUFDT_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/libufdt"
This info so I got all requirements to build the kerne. And do add path
properly check path using tab.
Saurabh Sakhare
On Mon, Mar 11, 2019 at 10:46 PM Emanuele Vannacci <
emanuele.vanna...@gmail.com> wrote:
> i have the same problem. Do you solve this error?
>
> Il giorno giovedì 15 novembre 2018 20:44:31 UTC+1, Lance Vick ha scritto:
>>
>> I am unable to build a kernel for crosshatch.
>>
>> Looks like a missing file or broken path?
>>
>> Also I am only assuming "android-msm-bluecross-4.9-pie-dr1-release" for
>> the branch and "sdm845-perf" for the defconfig from looking at git history
>> as there is no documentation for crosshatch or blueline in
>> https://source.android.com/setup/build/building-kernels
>>
>> Build commands:
>>
>> git clone https://android.googlesource.com/kernel/msm kernel/msm
>> cd "kernel/msm"
>> git checkout android-msm-bluecross-4.9-pie-dr1-release
>>
>> export ARCH=arm64
>> export
>> CROSS_COMPILE="$PWD/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-${gcc_version}/bin/aarch64-linux-android-"
>>
>> make "sdm845-perf_defconfig"
>> make -j8
>>
>>
>> Failure output:
>>
>> In file included from drivers/clk/qcom/mdss/mdss_pll_trace.h:116:0,
>>
>> from drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.c:24:
>>
>> ./include/trace/define_trace.h:88:43: fatal error: ./mdss_pll_trace.h: No
>> such file or directory
>> #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
>>
>> compilation terminated.
>>
>> scripts/Makefile.build:336: recipe for target
>> 'drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.o' failed
>> make[4]: *** [drivers/clk/qcom/mdss/mdss-dsi-pll-10nm.o] Error 1
>> make[4]: *** Waiting for unfinished jobs
>> scripts/Makefile.build:650: recipe for target 'drivers/clk/qcom/mdss'
>> failed
>> make[3]: *** [drivers/clk/qcom/mdss] Error 2
>> scripts/Makefile.build:650: recipe for target 'drivers/clk/qcom' failed
>> make[2]: *** [drivers/clk/qcom] Error 2
>> scripts/Makefile.build:650: recipe for target 'drivers/clk' failed
>> make[1]: *** [drivers/clk] Error 2
>> make[1]: *** Waiting for unfinished jobs
>>
>> create image file: arch/arm64/boot/dtbo.img...
>> Can not read file: arch/arm64/boot/dts/google/sdm845-v2-b1c1-devboard.dtbo
>> arch/arm64/boot/Makefile:71: recipe for target 'arch/arm64/boot/dtbo.img'
>> failed
>> make[1]: *** [arch/arm64/boot/dtbo.img] Error 255
>> arch/arm64/Makefile:214: recipe for target 'dtbo.img' failed
>> make: *** [dtbo.img] Error 2
>> make: *** Waiting for unfinished jobs
>>
>> Makefile:1117: recipe for target 'drivers' failed
>>
>> make: *** [drivers] Error 2
>>
>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
