1. meta-freescale@lists.yoctoproject.org
  2. Messages
   Date   
Re: OpenGL ES on i.MX8

Joshua Watt
 

On Mon, Sep 14, 2020 at 3:56 PM Peter Bergin <peter@...> wrote:

Hi Andy,

On 2020-09-14 13:20, Andy Pont wrote:
Trying to find an equivalent configuration for the i.MX8m I am unable
to find an equivalent method. The Vivante user space libraries don’t
seem to exist in a framebuffer or DRM form, instead they all seem to
require Wayland or X11.

Can someone more knowledgeable than I confirm whether that is the case
or whether I am missing something?

-Andy.
this is the statement from NXP
(https://source.codeaurora.org/external/imx/imx-manifest/tree/README?h=imx-linux-zeus#n53).
As seen they do not actively support the framebuffer distro for i.Mx8
targets on their official BSP.

The recipe for vivante user space lib imx-gpu-viv also have a guard for
mx8 that only builds it when wayland is enabled.
(https://github.com/Freescale/meta-freescale/blob/e0fa0255795ce584b3b5ad74c330cabeb0caa28d/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc#L60).

I'm also interested in the same question as you are as I'm in a start up
phase for a i.Mx8 project where we would like to run with OpenGL or
Vulkan directly against DRM and avoid display manager. Would be great to
hear someone from NXP give their picture of this. I have tried the NXP
community but without any info so far.
(https://community.nxp.com/t5/i-MX-Graphics/vulkan-without-display-server-Wayland-X11/m-p/1134083#M1)
FWIW, standing up a GLES/DRM/KMS application isn't terribly hard. I've
done it on an IMX8 before without too much trouble. kmscube is
probably the best place to start as it is a pretty complete example.

However, I would also highly recommend looking at running your
application under the weston (wayland) fullscreen shell. It's just as
powerful except you don't have to deal with all the twiddly DRM/KMS
APIs, and the "overhead" is pretty much non-existent because you
render directly to a DMA buf which weston presents to the display.


Best regards,
/Peter
Re: OpenGL ES on i.MX8

Peter Bergin
 

Hi Andy,

On 2020-09-14 13:20, Andy Pont wrote:
Trying to find an equivalent configuration for the i.MX8m I am unable to find an equivalent method.  The Vivante user space libraries don’t seem to exist in a framebuffer or DRM form, instead they all seem to require Wayland or X11.

Can someone more knowledgeable than I confirm whether that is the case or whether I am missing something?

-Andy.
this is the statement from NXP (https://source.codeaurora.org/external/imx/imx-manifest/tree/README?h=imx-linux-zeus#n53). As seen they do not actively support the framebuffer distro for i.Mx8 targets on their official BSP.

The recipe for vivante user space lib imx-gpu-viv also have a guard for mx8 that only builds it when wayland is enabled. (https://github.com/Freescale/meta-freescale/blob/e0fa0255795ce584b3b5ad74c330cabeb0caa28d/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc#L60).

I'm also interested in the same question as you are as I'm in a start up phase for a i.Mx8 project where we would like to run with OpenGL or Vulkan directly against DRM and avoid display manager. Would be great to hear someone from NXP give their picture of this. I have tried the NXP community but without any info so far. (https://community.nxp.com/t5/i-MX-Graphics/vulkan-without-display-server-Wayland-X11/m-p/1134083#M1)

Best regards,
/Peter
Re: OpenGL ES on i.MX8

Prabhu
 

I don’t it may be part of framebuffer distro. Application dependency to gbm should pull in libgbm.



On Sep 14, 2020 at 6:33 AM, <Andy Pont> wrote:

Prabhusundar wrote…

>i.MX8 has GBM(DRM) support which is alternative for the lagacy  
>framebuffer.
Does that use the standard fsl-framebuffer or fslc-framebuffer distro  
options from meta-freescale-distro as I have used before?

-Andy.

Re: OpenGL ES on i.MX8

Andy Pont <andy.pont@...>
 

Prabhusundar wrote…

i.MX8 has GBM(DRM) support which is alternative for the lagacy framebuffer.
Does that use the standard fsl-framebuffer or fslc-framebuffer distro options from meta-freescale-distro as I have used before?

-Andy.
Re: OpenGL ES on i.MX8

Prabhu
 

i.MX8 has GBM(DRM) support which is alternative for the lagacy framebuffer.


On Sep 14, 2020 at 6:20 AM, <Andy Pont> wrote:

Hello,

This is probably a question for NXP themselves but I thought I would try
the collective wisdom of the mailing list first.

When I build images for the i.MX6 I can build the OpenGL ES support to
use EGL and the Vivante driver to directly access the framebuffer
without having to include all of the overhead of X11 or Weston/Wayland.

Trying to find an equivalent configuration for the i.MX8m I am unable to
find an equivalent method.  The Vivante user space libraries don’t seem
to exist in a framebuffer or DRM form, instead they all seem to require
Wayland or X11.

Can someone more knowledgeable than I confirm whether that is the case
or whether I am missing something?

-Andy.

OpenGL ES on i.MX8

Andy Pont <andy.pont@...>
 

Hello,

This is probably a question for NXP themselves but I thought I would try the collective wisdom of the mailing list first.

When I build images for the i.MX6 I can build the OpenGL ES support to use EGL and the Vivante driver to directly access the framebuffer without having to include all of the overhead of X11 or Weston/Wayland.

Trying to find an equivalent configuration for the i.MX8m I am unable to find an equivalent method. The Vivante user space libraries don’t seem to exist in a framebuffer or DRM form, instead they all seem to require Wayland or X11.

Can someone more knowledgeable than I confirm whether that is the case or whether I am missing something?

-Andy.
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Brian Hutchinson
 

On Fri, Sep 11, 2020 at 02:29 AM, Andrey Zhizhikin wrote:
On Thu, Sep 10, 2020 at 11:59 PM Brian Hutchinson <b.hutchman@...> wrote:
On Thu, Sep 10, 2020 at 05:22 AM, Fabio Estevam wrote:

Hi Otavio,

On Thu, Sep 10, 2020 at 9:09 AM Otavio Salvador
<otavio.salvador@...> wrote:

Could U-Boot load the correct dtb for the board revision?

Unfortunately, this cannot be determined in run-time.

When the sdcard is created, the u-boot environment has fdt_file defaulted to imx8mm-evk.dtb. I've not yet figured out how to override the recipe to specify which .dtb file should be used.
You can try to do something like this in your layer via creating a
u-boot-imx_%.bbapend:

patch_uboot_defconfig () {
sed -i -e '/^[ ]*CONFIG_DEFAULT_FDT_FILE[ ]*=/d' ${S}/configs/$1
echo 'CONFIG_DEFAULT_FDT_FILE="'$2'"' >>${S}/configs/$1
}

do_configure_prepend_imx8mmevk () {
patch_uboot_defconfig imx8mm_evk_defconfig imx8mm-evk-revb.dtb
}

NOTE: This is not the most clean solution on how to approach the

Ha, ha, I figured there was already some way to do it and I just overlooked it or wasn't smart enough to figure it out.  Yeah, you can do anything with good ole sed. 

I plan to switch back to using the original .config and try the rev B .dtb to see if that fixes things when I get a chance.

setting of U-Boot DTB and would (most probably) break reproducibility.
You can use it to see what should be changed, and try out if that
would solve the PCIe hang during boot. Also: "For verification
purposes ONLY!". :)

Thanks!

Brian
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Andrey Zhizhikin
 

On Thu, Sep 10, 2020 at 11:59 PM Brian Hutchinson <b.hutchman@...> wrote:

On Thu, Sep 10, 2020 at 05:22 AM, Fabio Estevam wrote:

Hi Otavio,

On Thu, Sep 10, 2020 at 9:09 AM Otavio Salvador
<otavio.salvador@...> wrote:

Could U-Boot load the correct dtb for the board revision?

Unfortunately, this cannot be determined in run-time.

When the sdcard is created, the u-boot environment has fdt_file defaulted to imx8mm-evk.dtb. I've not yet figured out how to override the recipe to specify which .dtb file should be used.
You can try to do something like this in your layer via creating a
u-boot-imx_%.bbapend:

patch_uboot_defconfig () {
sed -i -e '/^[ ]*CONFIG_DEFAULT_FDT_FILE[ ]*=/d' ${S}/configs/$1
echo 'CONFIG_DEFAULT_FDT_FILE="'$2'"' >>${S}/configs/$1
}

do_configure_prepend_imx8mmevk () {
patch_uboot_defconfig imx8mm_evk_defconfig imx8mm-evk-revb.dtb
}

NOTE: This is not the most clean solution on how to approach the
setting of U-Boot DTB and would (most probably) break reproducibility.
You can use it to see what should be changed, and try out if that
would solve the PCIe hang during boot. Also: "For verification
purposes ONLY!". :)

For sdcard boot, all of the .dtb's are on the FAT partition of the sdcard so it's easy enough to change the filename to use.

I use SPI NOR so I just have the .dtb file burned into a specific address so the name doesn't matter in that case.

Regards,

Brian


--
Regards,
Andrey.
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Brian Hutchinson
 

On Thu, Sep 10, 2020 at 05:22 AM, Fabio Estevam wrote:
Hi Otavio,

On Thu, Sep 10, 2020 at 9:09 AM Otavio Salvador
<otavio.salvador@...> wrote:

Could U-Boot load the correct dtb for the board revision?
Unfortunately, this cannot be determined in run-time.
When the sdcard is created, the u-boot environment has fdt_file defaulted to imx8mm-evk.dtb.  I've not yet figured out how to override the recipe to specify which .dtb file should be used.  For sdcard boot, all of the .dtb's are on the FAT partition of the sdcard so it's easy enough to change the filename to use.

I use SPI NOR so I just have the .dtb file burned into a specific address so the name doesn't matter in that case.

Regards,

Brian
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Fabio Estevam
 

Hi Otavio,

On Thu, Sep 10, 2020 at 9:09 AM Otavio Salvador
<otavio.salvador@...> wrote:

Could U-Boot load the correct dtb for the board revision?
Unfortunately, this cannot be determined in run-time.
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Otavio Salvador
 

Hello Fabio,

Em qui., 10 de set. de 2020 às 09:03, Fabio Estevam
<festevam@...> escreveu:
On Thu, Sep 10, 2020 at 8:54 AM Otavio Salvador
<otavio.salvador@...> wrote:

Hello all,

Em qui., 10 de set. de 2020 às 05:12, Carlos Rafael Giani
<crg7475@...> escreveu:
I have the same problem. imx8mmevk does not boot with Yocto Dunfell. Booting stops at "PCIe PLL lock timeout" or "Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0". I tried booting from MMC and from NFS, and neither work.
On 29.07.20 17:56, Brian Hutchinson wrote:
...
[ 2.183627] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[ 2.189835] random: fast init done
[ 2.208107] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout
Do you have a revB board?

If so, please use imx8mm-evk-revb.dtb instead as there is a difference
between revB versus revC that is related to the PCIe clock source.

From arch/arm64/boot/dts/freescale/imx8mm-evk-revb.dts:

/*
* External OSC is used as PCIe REFCLK on RevC board.
* Use the -revb.dts file to distiguish the different
* HW design.
*/
&pcie0{
ext_osc = <0>;
status = "okay";
};
Could U-Boot load the correct dtb for the board revision?


--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Fabio Estevam
 

Hi Carlos,

On Thu, Sep 10, 2020 at 8:54 AM Otavio Salvador
<otavio.salvador@...> wrote:

Hello all,

Em qui., 10 de set. de 2020 às 05:12, Carlos Rafael Giani
<crg7475@...> escreveu:
I have the same problem. imx8mmevk does not boot with Yocto Dunfell. Booting stops at "PCIe PLL lock timeout" or "Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0". I tried booting from MMC and from NFS, and neither work.
On 29.07.20 17:56, Brian Hutchinson wrote:
...
[ 2.183627] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[ 2.189835] random: fast init done
[ 2.208107] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout
Do you have a revB board?

If so, please use imx8mm-evk-revb.dtb instead as there is a difference
between revB versus revC that is related to the PCIe clock source.

From arch/arm64/boot/dts/freescale/imx8mm-evk-revb.dts:

/*
* External OSC is used as PCIe REFCLK on RevC board.
* Use the -revb.dts file to distiguish the different
* HW design.
*/
&pcie0{
ext_osc = <0>;
status = "okay";
};
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Otavio Salvador
 

Hello all,

Em qui., 10 de set. de 2020 às 05:12, Carlos Rafael Giani
<crg7475@...> escreveu:
I have the same problem. imx8mmevk does not boot with Yocto Dunfell. Booting stops at "PCIe PLL lock timeout" or "Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0". I tried booting from MMC and from NFS, and neither work.
On 29.07.20 17:56, Brian Hutchinson wrote:
...
[ 2.183627] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[ 2.189835] random: fast init done
[ 2.208107] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout
Could you guys open an issue on github about this?

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
Re: Latest build of fsl-community-bsp kernel hangs booting imx8mmevk

Carlos Rafael Giani
 

I have the same problem. imx8mmevk does not boot with Yocto Dunfell. Booting stops at "PCIe PLL lock timeout" or "Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0". I tried booting from MMC and from NFS, and neither work.


On 29.07.20 17:56, Brian Hutchinson wrote:

Hi,

Bottom line up front, built fsl-community-bsp dunfell for imx8mmevk and Linux 5.4 kernel hangs on boot.

So far I've been NXP official releases.  I really needed the 5.4 kernel so was excited when I saw they did a release but just learned that their releases are only for certain boards and not necessarily backward compatible with older boards.

I learned the above after I built NXP Zeus 5.4 release of core-image-base and put generated sdcard in my bare (I don't have video, touch screen etc., it's just a bare board that was a hand-me-down but works fine with Sumo release) Rev B (sticker on the bottom) imx8mmevk board and the console showed kernel hanging on boot.

So then I built the fsl-community-bsp version for imx8mmevk using both Poky and fscl-wayland distros.  I built core-image-minimal for poky and core-image-base for fscl-wayland.

All three hang in the same place on boot.  I'll copy and paste console output below but does anyone have a clue why it's hanging?  I suspect it's because device tree is looking for something I don't have plugged up to the board ... but I would think it should boot on a bare board like previous versions did.

Thanks for any clues!

Regards,

Brian

Console output booting from sdcard ... This is fsl-community-bsp core-image-base for fscl-wayland (but again, all three images I built did the same thing):

U-Boot SPL 2019.04-lf-5.4.y_v2019.04+g228843cdf5 (Feb 22 2020 - 12:25:23 +0000)
power_bd71837_init
DDRINFO: start DRAM init
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1


U-Boot 2019.04-lf-5.4.y_v2019.04+g228843cdf5 (Feb 22 2020 - 12:25:23 +0000)

CPU:   Freescale i.MX8MMQ rev1.0 at 1200MHz
CPU:   Commercial temperature grade (0C to 95C) at 33C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM:  2 GiB
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Run CMD11 1.8V switch
*** Warning - bad CRC, using default environment

No panel detected: default to MIPI2HDMI
adv7535_init: Can't find device id=0x3d, on bus 1
Display: MIPI2HDMI (1920x1080)
Video: 1920x1080x24
In:    serial
Out:   serial
Err:   serial

 BuildInfo:
  - ATF 7b3389d
  - U-Boot 2019.04-lf-5.4.y_v2019.04+g228843cdf5

Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Run CMD11 1.8V switch
Net:  
Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Run CMD11 1.8V switch
26550784 bytes read in 652 ms (38.8 MiB/s)
Booting from mmc ...
43520 bytes read in 5 ms (8.3 MiB/s)
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Using Device Tree in place at 0000000043000000, end 000000004300d9ff

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.3+g66d6cfd8712d (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Wed Feb 26 09:13:26 UTC 2020
[    0.000000] Machine model: FSL i.MX8MM EVK board
[    0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options '115200')
[    0.000000] printk: bootconsole [ec_imx6q0] enabled
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000078000000, size 640 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbdd500-0xbdbdefff]
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000b7ffffff]
[    0.000000]   node   0: [mem 0x00000000b8400000-0x00000000bdffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 24 pages/cpu s58840 r8192 d31272 u98304
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 507008
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200 root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1337460K/2060288K available (15740K kernel code, 1160K rwdata, 6172K rodata, 2816K init, 1008K bss, 67468K reserved, 655360K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x44c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.008434] Console: colour dummy device 80x25
[    0.012581] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.022845] pid_max: default: 32768 minimum: 301
[    0.027546] LSM: Security Framework initializing
[    0.032166] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.039562] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.071499] ASID allocator initialised with 32768 entries
[    0.079495] rcu: Hierarchical SRCU implementation.
[    0.088277] EFI services will not be available.
[    0.095519] smp: Bringing up secondary CPUs ...
[    0.127675] Detected VIPT I-cache on CPU1
[    0.127702] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.127734] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.159701] Detected VIPT I-cache on CPU2
[    0.159717] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.159736] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.191742] Detected VIPT I-cache on CPU3
[    0.191756] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.191772] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.191828] smp: Brought up 1 node, 4 CPUs
[    0.245581] SMP: Total of 4 processors activated.
[    0.250302] CPU features: detected: 32-bit EL0 Support
[    0.255473] CPU features: detected: CRC32 instructions
[    0.267175] CPU: All CPU(s) started at EL2
[    0.268429] alternatives: patching kernel code
[    0.274282] devtmpfs: initialized
[    0.282038] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.288978] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.311783] pinctrl core: initialized pinctrl subsystem
[    0.314874] DMI not present or invalid.
[    0.318261] NET: Registered protocol family 16
[    0.335499] DMA: preallocated 256 KiB pool for atomic allocations
[    0.338792] audit: initializing netlink subsys (disabled)
[    0.344417] audit: type=2000 audit(0.296:1): state=initialized audit_enabled=0 res=1
[    0.352000] cpuidle: using governor menu
[    0.356362] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.363424] Serial: AMBA PL011 UART driver
[    0.366908] imx mu driver is registered.
[    0.370794] imx rpmsg driver is registered.
[    0.379964] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.401819] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.405704] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.412457] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.419169] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.427447] cryptd: max_cpu_qlen set to 1000
[    0.435224] ACPI: Interpreter disabled.
[    0.437074] iommu: Default domain type: Translated
[    0.441240] vgaarb: loaded
[    0.444084] SCSI subsystem initialized
[    0.447897] usbcore: registered new interface driver usbfs
[    0.453368] usbcore: registered new interface driver hub
[    0.458479] usbcore: registered new device driver usb
[    0.464654] mc: Linux media interface: v0.10
[    0.467834] videodev: Linux video capture interface: v2.00
[    0.473373] pps_core: LinuxPPS API ver. 1 registered
[    0.478298] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@...>
[    0.487492] PTP clock support registered
[    0.491547] EDAC MC: Ver: 3.0.0
[    0.495294] No BMan portals available!
[    0.498577] QMan: Allocated lookup table at (____ptrval____), entry count 65537
[    0.505918] No QMan portals available!
[    0.509792] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
[    0.515865] FPGA manager framework
[    0.518964] Advanced Linux Sound Architecture Driver Initialized.
[    0.525354] Bluetooth: Core ver 2.22
[    0.528624] NET: Registered protocol family 31
[    0.533074] Bluetooth: HCI device and connection manager initialized
[    0.539464] Bluetooth: HCI socket layer initialized
[    0.544361] Bluetooth: L2CAP socket layer initialized
[    0.549442] Bluetooth: SCO socket layer initialized
[    0.554986] clocksource: Switched to clocksource arch_sys_counter
[    0.560629] VFS: Disk quotas dquot_6.6.0
[    0.564446] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.571458] pnp: PnP ACPI: disabled
[    0.579848] thermal_sys: Registered thermal governor 'step_wise'
[    0.579851] thermal_sys: Registered thermal governor 'power_allocator'
[    0.583327] NET: Registered protocol family 2
[    0.594272] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.602576] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.610607] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.618078] TCP: Hash tables configured (established 16384 bind 16384)
[    0.624489] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.631189] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.638462] NET: Registered protocol family 1
[    0.643094] RPC: Registered named UNIX socket transport module.
[    0.648655] RPC: Registered udp transport module.
[    0.653381] RPC: Registered tcp transport module.
[    0.658100] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.664935] PCI: CLS 0 bytes, default 64
[    0.669187] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.676652] kvm [1]: IPA Size Limit: 40bits
[    0.681065] kvm [1]: GICv3: no GICV resource entry
[    0.685315] kvm [1]: disabling GICv2 emulation
[    0.689789] kvm [1]: GIC system register CPU interface enabled
[    0.695696] kvm [1]: vgic interrupt IRQ1
[    0.699666] kvm [1]: Hyp mode initialized successfully
[    0.709762] Initialise system trusted keyrings
[    0.711474] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.723095] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.726681] NFS: Registering the id_resolver key type
[    0.731194] Key type id_resolver registered
[    0.735370] Key type id_legacy registered
[    0.739400] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.746146] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[    0.752594] 9p: Installing v9fs 9p2000 file system support
[    0.771208] Key type asymmetric registered
[    0.772449] Asymmetric key parser 'x509' registered
[    0.777388] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.784795] io scheduler mq-deadline registered
[    0.789341] io scheduler kyber registered
[    0.797601] EINJ: ACPI disabled.
[    0.804956] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.812610] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.837546] mxs-dma 33000000.dma-controller: initialized
[    0.841110] Bus freq driver module loaded
[    0.848749] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.854186] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 37, base_baud = 5000000) is a IMX
[    0.861497] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 38, base_baud = 5000000) is a IMX
[    0.870209] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 39, base_baud = 1500000) is a IMX
[    0.878739] printk: console [ttymxc1] enabled
[    0.878739] printk: console [ttymxc1] enabled
[    0.887397] printk: bootconsole [ec_imx6q0] disabled
[    0.887397] printk: bootconsole [ec_imx6q0] disabled
[    0.900987] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.907625] [drm] No driver support for vblank timestamp query.
[    0.913623] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[    0.923032] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    0.930069] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    0.938345] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
[    0.946123] imx-drm soc@0:bus@32c00000:display-subsystem: failed to bind 32e10000.mipi_dsi (ops imx_sec_dsim_ops): -517
[    0.956993] imx-drm soc@0:bus@32c00000:display-subsystem: master bind failed: -517
[    0.973174] loop: module loaded
[    0.978250] imx ahci driver is registered.
[    0.985177] spi-nor spi3.0: n25q256ax1 (32768 Kbytes)
[    0.996701] libphy: Fixed MDIO Bus: probed
[    1.001457] tun: Universal TUN/TAP device driver, 1.6
[    1.007183] thunder_xcv, ver 1.0
[    1.010441] thunder_bgx, ver 1.0
[    1.013703] nicpf, ver 1.0
[    1.017279] pps pps0: new PPS source ptp0
[    1.026195] libphy: fec_enet_mii_bus: probed
[    1.031586] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.038084] Freescale FM module, FMD API version 21.1.0
[    1.043545] Freescale FM Ports module
[    1.047215] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    1.052927] fsl_dpa: FSL DPAA Ethernet driver
[    1.057390] fsl_advanced: FSL DPAA Advanced drivers:
[    1.062360] fsl_proxy: FSL DPAA Proxy initialization driver
[    1.068029] fsl_oh: FSL FMan Offline Parsing port driver
[    1.074131] hclge is initializing
[    1.077456] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    1.084682] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.090034] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    1.097087] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.102863] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.108698] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.114655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    1.121621] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.127230] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.135063] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.141126] sky2: driver version 1.30
[    1.145209] VFIO - User Level meta-driver version: 0.3
[    1.151914] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.158452] ehci-pci: EHCI PCI platform driver
[    1.162969] ehci-platform: EHCI generic platform driver
[    1.168359] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.174562] ohci-pci: OHCI PCI platform driver
[    1.179040] ohci-platform: OHCI generic platform driver
[    1.184762] usbcore: registered new interface driver usb-storage
[    1.192151] imx_usb 32e40000.usb: No over current polarity defined
[    1.199613] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/soc@0:bus@30000000/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.214519] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.220795] i2c /dev entries driver
[    1.224891] mx6s-csi 32e20000.csi1_bridge: initialising
[    1.230614] mxc_mipi-csi 32e30000.mipi_csi: 32e30000.mipi_csi supply mipi-phy not found, using dummy regulator
[    1.240807] mxc_mipi-csi 32e30000.mipi_csi: mipi csi v4l2 device registered
[    1.247780] CSI: Registered sensor subdevice: mxc_mipi-csi.0
[    1.253463] mxc_mipi-csi 32e30000.mipi_csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 333000000
[    1.267270] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.273840] Bluetooth: HCI UART driver ver 2.3
[    1.278296] Bluetooth: HCI UART protocol H4 registered
[    1.283439] Bluetooth: HCI UART protocol BCSP registered
[    1.288772] Bluetooth: HCI UART protocol LL registered
[    1.293916] Bluetooth: HCI UART protocol ATH3K registered
[    1.299332] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.305687] Bluetooth: HCI UART protocol Broadcom registered
[    1.311367] Bluetooth: HCI UART protocol QCA registered
[    1.318164] sdhci: Secure Digital Host Controller Interface driver
[    1.324359] sdhci: Copyright(c) Pierre Ossman
[    1.328893] Synopsys Designware Multimedia Card Interface Driver
[    1.335433] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.341820] mmc0: CQHCI version 5.10
[    1.345793] mmc1: CQHCI version 5.10
[    1.349814] mmc2: CQHCI version 5.10
[    1.384511] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.394542] ledtrig-cpu: registered to indicate activity on CPUs
[    1.401590] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.408312] caam 30900000.crypto: job rings = 3, qi = 0
[    1.439426] caam algorithms registered in /proc/crypto
[    1.449584] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.459164] caam_jr 30901000.jr0: registering rng-caam
[    1.477830] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.483735] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.492521] usbcore: registered new interface driver usbhid
[    1.498116] usbhid: USB HID core driver
[    1.504206] No fsl,qman node
[    1.507112] Freescale USDPAA process driver
[    1.511300] fsl-usdpaa: no region found
[    1.515171] Freescale USDPAA process IRQ driver
[    1.524394] optee: probing for conduit method from DT.
[    1.529581] optee: revision 3.2 (6d99b525)
[    1.530993] optee: dynamic shared memory is enabled
[    1.540123] optee: initialized driver
[    1.545372] hantrodec 0 : module inserted. Major = 236
[    1.550942] hantrodec 1 : module inserted. Major = 236
[    1.556994] hx280enc: module inserted. Major <235>
[    1.557183] mmc2: Command Queue Engine enabled
[    1.565237] wm8524-codec audio-codec: Failed to get mute line: -517
[    1.566322] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.574705] fsl-sai 30030000.sai: failed to get mclk0 clock: -2
[    1.579851] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.589553] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.594217] fsl-micfil-dai 30080000.micfil: GET IRQ: 14
[    1.595643] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.600733] fsl-micfil-dai 30080000.micfil: GET IRQ: 15
[    1.607427] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)
[    1.611879] fsl-micfil-dai 30080000.micfil: GET IRQ: 16
[    1.621780]  mmcblk2: p1
[    1.624427] fsl-micfil-dai 30080000.micfil: GET IRQ: 17
[    1.636692] imx-spdif sound-spdif: snd-soc-dummy-dai <-> 30090000.spdif mapping ok
[    1.644303] imx-spdif sound-spdif: ASoC: no DMI vendor name!
[    1.652764] imx-ak4458 sound-ak4458: ASoC: failed to init link ak4458: -517
[    1.659748] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-517)
[    1.667124] debugfs: Directory '30080000.micfil' with parent 'imx-audio-micfil' already present!
[    1.676011] imx-micfil sound-micfil: snd-soc-dummy-dai <-> 30080000.micfil mapping ok
[    1.683854] imx-micfil sound-micfil: ASoC: no DMI vendor name!
[    1.691125] NET: Registered protocol family 26
[    1.696093] NET: Registered protocol family 10
[    1.701560] Segment Routing with IPv6
[    1.705292] NET: Registered protocol family 17
[    1.709837] Bluetooth: RFCOMM TTY layer initialized
[    1.714735] Bluetooth: RFCOMM socket layer initialized
[    1.719901] Bluetooth: RFCOMM ver 1.11
[    1.723661] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.728977] Bluetooth: BNEP filters: protocol multicast
[    1.734208] Bluetooth: BNEP socket layer initialized
[    1.739179] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.745106] Bluetooth: HIDP socket layer initialized
[    1.750102] 8021q: 802.1Q VLAN Support v1.8
[    1.754306] lib80211: common routines for IEEE802.11 drivers
[    1.760077] 9pnet: Installing 9P2000 support
[    1.764378] tsn generic netlink module v1 init...
[    1.769143] Key type dns_resolver registered
[    1.774425] registered taskstats version 1
[    1.778541] Loading compiled-in X.509 certificates
[    1.804566] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    1.813365] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    1.833813] LDO1: Bringing 1800000uV into 3000000-3000000uV
[    1.840372] LDO2: Bringing 800000uV into 900000-900000uV
[    1.848092] ldo6: supplied by regulator-dummy
[    1.853243] i2c i2c-0: IMX I2C adapter registered
[    1.859121] adv7511 1-003d: 1-003d supply avdd not found, using dummy regulator
[    1.866490] adv7511 1-003d: 1-003d supply dvdd not found, using dummy regulator
[    1.873843] adv7511 1-003d: 1-003d supply pvdd not found, using dummy regulator
[    1.881192] adv7511 1-003d: 1-003d supply a2vdd not found, using dummy regulator
[    1.888625] adv7511 1-003d: 1-003d supply v3p3 not found, using dummy regulator
[    1.895991] adv7511 1-003d: 1-003d supply v1p2 not found, using dummy regulator
[    1.904086] adv7511 1-003d: Probe failed. Remote port 'mipi_dsi@32e10000' disabled
[    1.913420] i2c i2c-1: IMX I2C adapter registered
[    1.919166] pca953x 2-0020: reg get err: -19
[    1.925749] ak4458 2-0010: Failed to request supplies: -517
[    1.931644] ak4458 2-0012: Failed to request supplies: -517
[    1.937486] ak5558 2-0013: Failed to request supplies: -517
[    1.943344] ak4458 2-0011: Failed to request supplies: -517
[    1.949205] ov5640_mipi 2-003c: No sensor reset pin available
[    1.955003] ov5640_mipi 2-003c: 2-003c supply DOVDD not found, using dummy regulator
[    1.962806] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator
[    1.970514] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator
[    1.987279] ov5640_mipi 2-003c: Read reg error: reg=300a
[    1.992604] ov5640_mipi 2-003c: Camera is not found
[    1.997630] i2c i2c-2: IMX I2C adapter registered                                                                                          
[    2.003730] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).                                                                    
[    2.003801] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator                                        
[    2.010360] [drm] No driver support for vblank timestamp query.                                                                            
[    2.010424] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)                                      
[    2.019768] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    2.025601] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    2.034711] imx6q-pcie 33800000.pcie:    IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[    2.041954] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    2.048871] imx6q-pcie 33800000.pcie:   MEM 0x18000000..0x1fefffff -> 0x18000000
[    2.056259] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -19
[    2.064585] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!.
[    2.071954] imx-drm soc@0:bus@32c00000:display-subsystem: failed to bind 32e10000.mipi_dsi (ops imx_sec_dsim_ops): -19
[    2.095937] imx-drm soc@0:bus@32c00000:display-subsystem: master bind failed: -19
[    2.104494] imx_usb 32e40000.usb: No over current polarity defined
[    2.110757] imx_usb 32e40000.usb: 32e40000.usb supply vbus not found, using dummy regulator
[    2.123616] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1
[    2.135787] mmc0: CQHCI version 5.10
[    2.171858] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA
[    2.179983] mmc1: CQHCI version 5.10
[    2.183627] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    2.189835] random: fast init done
[    2.208107] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout


    

  


					


				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Re: Build error of perf
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    leimaohui
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Hi, Yang

The following is the status of linux-qoriq that I'm using:
-------------------------------------
tmp/work-shared/ubinux-armv8/kernel-source$ git branch
* (HEAD detached at 134788b16485)
  Master
-------------------------------------

Best regards
Lei

				
					
					

					

						
-----Original Message-----
From: Zhenhua Luo <zhenhua.luo@...>
Sent: Tuesday, September 8, 2020 10:16 AM
To: Lei, Maohui <leimaohui@...>; Andrey Zhizhikin
<andrey.z@...>
Cc: meta-freescale@...
Subject: RE: [meta-freescale] Build error of perf

Hi Lei,

May I know which branch you are using?


Best Regards,

Zhenhua

-----Original Message-----
From: meta-freescale@... <meta-
freescale@...> On Behalf Of leimaohui via
lists.yoctoproject.org
Sent: Tuesday, September 8, 2020 10:09 AM
To: Andrey Zhizhikin <andrey.z@...>
Cc: meta-freescale@...
Subject: Re: [meta-freescale] Build error of perf

Hi, Andrey

I guess you're not building the latest meta-freescale, since the
latest version of kernel recipes (linux-fslc and linux-fslc-imx)
contains version v5.4.62. Or it is possible that you're building
linux-imx kernel, in which case you would have to port the patch on
top of
your tree.

I'm using linux-qoriq and I have updated to the newest commit of meta-
freescale.

Best regards
Lei

-----Original Message-----
From: Andrey Zhizhikin <andrey.z@...>
Sent: Monday, September 7, 2020 4:20 PM
To: Lei, Maohui <leimaohui@...>
Cc: meta-freescale@...
Subject: Re: [meta-freescale] Build error of perf

Hello Lei,

On Mon, Sep 7, 2020 at 7:37 AM leimaohui <leimaohui@...>
wrote:

Hi,

By latest meta-freescale, perf build failed, the error is as following:

---------------------------------------------
aarch64-ubinux-linux-ld:
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8
-u
bi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/pe
rf
/1
.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple
definition of `runtime';
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8
-u
bi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/p
er
f/
1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined
here
aarch64-ubinux-linux-ld: /ubinux-dev/
build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0
-r
9/perf-
1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end';
/ubinux-dev/
/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.
0-
r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here ......
---------------------------------------------

It seems that the repository has to merge the following patch:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
lk
ml.org%2Flkml%2F2020%2F3%2F4%2F313&amp;data=02%7C01%7Czhenhua.
lu
o%40
nxp.com%7C63f43673235e4dd22bc008d8539c24f4%7C686ea1d3bc2b4c6fa9
2c
d99
c5c301635%7C0%7C0%7C637351277383842133&amp;sdata=Qm7fCOHUJ7J
O3
eb2z%2
BxQ97ke6sGZJRFhjIJfyuMVtSo%3D&amp;reserved=0
This is covered by [df35e878d0a51755fb500e2e8e29c7ebb0239756]
which
is present in the kernel tree and came in with v5.4.56.

I guess you're not building the latest meta-freescale, since the
latest version of kernel recipes (linux-fslc and linux-fslc-imx)
contains version v5.4.62. Or it is possible that you're building
linux-imx kernel, in which case you would have to port the patch on
top of
your tree.


Best regards
Lei





--
Regards,
Andrey.

					


				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Re: Build error of perf
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    Zhenhua Luo
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Hi Lei, 

May I know which branch you are using? 


Best Regards, 

Zhenhua

				
					
					

					

						
-----Original Message-----
From: meta-freescale@... <meta-
freescale@...> On Behalf Of leimaohui via
lists.yoctoproject.org
Sent: Tuesday, September 8, 2020 10:09 AM
To: Andrey Zhizhikin <andrey.z@...>
Cc: meta-freescale@...
Subject: Re: [meta-freescale] Build error of perf

Hi, Andrey

I guess you're not building the latest meta-freescale, since the
latest version of kernel recipes (linux-fslc and linux-fslc-imx)
contains version v5.4.62. Or it is possible that you're building
linux-imx kernel, in which case you would have to port the patch on top of
your tree.

I'm using linux-qoriq and I have updated to the newest commit of meta-
freescale.

Best regards
Lei

-----Original Message-----
From: Andrey Zhizhikin <andrey.z@...>
Sent: Monday, September 7, 2020 4:20 PM
To: Lei, Maohui <leimaohui@...>
Cc: meta-freescale@...
Subject: Re: [meta-freescale] Build error of perf

Hello Lei,

On Mon, Sep 7, 2020 at 7:37 AM leimaohui <leimaohui@...>
wrote:

Hi,

By latest meta-freescale, perf build failed, the error is as following:

---------------------------------------------
aarch64-ubinux-linux-ld:
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-u
bi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf
/1
.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition
of `runtime';
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-u
bi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/per
f/
1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
aarch64-ubinux-linux-ld: /ubinux-dev/
build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r
9/perf-
1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end';
/ubinux-dev/
/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-
r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here ......
---------------------------------------------

It seems that the repository has to merge the following patch:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flk
ml.org%2Flkml%2F2020%2F3%2F4%2F313&amp;data=02%7C01%7Czhenhua.lu
o%40
nxp.com%7C63f43673235e4dd22bc008d8539c24f4%7C686ea1d3bc2b4c6fa92c
d99
c5c301635%7C0%7C0%7C637351277383842133&amp;sdata=Qm7fCOHUJ7JO3
eb2z%2
BxQ97ke6sGZJRFhjIJfyuMVtSo%3D&amp;reserved=0
This is covered by [df35e878d0a51755fb500e2e8e29c7ebb0239756] which is
present in the kernel tree and came in with v5.4.56.

I guess you're not building the latest meta-freescale, since the
latest version of kernel recipes (linux-fslc and linux-fslc-imx)
contains version v5.4.62. Or it is possible that you're building
linux-imx kernel, in which case you would have to port the patch on top of
your tree.


Best regards
Lei





--
Regards,
Andrey.

					


				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Re: Build error of perf
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    leimaohui
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Hi, Andrey

I guess you're not building the latest meta-freescale, since the latest version of
kernel recipes (linux-fslc and linux-fslc-imx) contains version v5.4.62. Or it is
possible that you're building linux-imx kernel, in which case you would have to
port the patch on top of your tree.
I'm using linux-qoriq and I have updated to the newest commit of meta-freescale.

Best regards
Lei 

-----Original Message-----
From: Andrey Zhizhikin <andrey.z@...>
Sent: Monday, September 7, 2020 4:20 PM
To: Lei, Maohui <leimaohui@...>
Cc: meta-freescale@...
Subject: Re: [meta-freescale] Build error of perf

Hello Lei,

On Mon, Sep 7, 2020 at 7:37 AM leimaohui <leimaohui@...>
wrote:

Hi,

By latest meta-freescale, perf build failed, the error is as following:

---------------------------------------------
aarch64-ubinux-linux-ld:
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1
.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of
`runtime';
/ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubi
nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/
1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
aarch64-ubinux-linux-ld: /ubinux-dev/
build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-
1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end'; /ubinux-dev/
/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-
linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-
r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here ......
---------------------------------------------

It seems that the repository has to merge the following patch:
https://lkml.org/lkml/2020/3/4/313
This is covered by [df35e878d0a51755fb500e2e8e29c7ebb0239756] which is
present in the kernel tree and came in with v5.4.56.

I guess you're not building the latest meta-freescale, since the latest version of
kernel recipes (linux-fslc and linux-fslc-imx) contains version v5.4.62. Or it is
possible that you're building linux-imx kernel, in which case you would have to
port the patch on top of your tree.


Best regards
Lei





--
Regards,
Andrey.

				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Re: Build error of perf
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    Andrey Zhizhikin
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Hello Lei,

On Mon, Sep 7, 2020 at 7:37 AM leimaohui <leimaohui@...> wrote:

Hi,

By latest meta-freescale, perf build failed, the error is as following:

---------------------------------------------
aarch64-ubinux-linux-ld: /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `runtime'; /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
aarch64-ubinux-linux-ld: /ubinux-dev/ build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end'; /ubinux-dev/ /build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
......
---------------------------------------------

It seems that the repository has to merge the following patch:
https://lkml.org/lkml/2020/3/4/313
This is covered by [df35e878d0a51755fb500e2e8e29c7ebb0239756] which is
present in the kernel tree and came in with v5.4.56.

I guess you're not building the latest meta-freescale, since the
latest version of kernel recipes (linux-fslc and linux-fslc-imx)
contains version v5.4.62. Or it is possible that you're building
linux-imx kernel, in which case you would have to port the patch on
top of your tree.


Best regards
Lei





-- 
Regards,
Andrey.

				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Build error of perf
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    leimaohui
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Hi,

By latest meta-freescale, perf build failed, the error is as following:

---------------------------------------------
aarch64-ubinux-linux-ld: /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `runtime'; /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
aarch64-ubinux-linux-ld: /ubinux-dev/ build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end'; /ubinux-dev/ /build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
......
---------------------------------------------

It seems that the repository has to merge the following patch:
https://lkml.org/lkml/2020/3/4/313

Best regards
Lei

				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
			
				
	
		
	

		
			
			

			
			
				
				

					

						
							
							

							Re: imx51evk and Zeus
							
						
					

				

				

			
			

				

					


						
							
								
	
		
			
		
		
  
	
    Otavio Salvador
	

	

							
						
					

					

						
							


						
						 
						
							
							
						
						
					

				

			

			

			

				
Em ter., 25 de ago. de 2020 às 11:13, Mauro Ziliani
<mauro@...> escreveu:
Thank you for the answer.

For imx51evk which u-boot is better? u-boot-fslc or u-boot-imx?
u-boot-imx does not officially support it, so u-boot-fslc is the best call here.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

				
				
				
			

			
			

				
	


		
	

		
			

				

				

				
					

						

							
							
						

					

				

			
			

				

					

				

			

			
				
		
		

		
		
	


	

			
		
	

	

		
		
		
		
		
	

	

		
		
		
		
		
	

	
	

		
		
		
		
	



	

		

			
	
		

			

				

					
						
							501 - 520 of 24910