Yocto build for wandboard with local kernel

1,766 views
Skip to first unread message

u2bpavankumar

unread,
Feb 1, 2015, 1:13:59 AM2/1/15
to wand...@googlegroups.com
Hi,

I have just received my wandboar-quad board and started to work on it. I have put the yocto image from their website onto sd card and was able to boot the device.

I wanted to build my own yocto image. For that I have followed the instruction as per http://wiki.wandboard.org/Getting_started_with_Yocto_on_Wandboard and was able to generate the image.

Now I want to modify the recipes to point to a local kernel instead of downloading from git. I have gone through the yocto user manual and some other stuff on net to see how to point to a local kernel.., I read somewhere that I need to set SRC_URI/DL_DIR etc.., but no clear instructions like in which file at what location I need to set these things.

I can see the recipe for kernel at following location

$/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb

and below is the content of the file

# adapted from linux-imx.inc, copyright (C) 2012-2013 O.S. Systems Software LTDA
# Released under the MIT license (see COPYING.MIT for the terms)

include linux-wandboard.inc

# Wandboard branch - based on 4.0.0 from Freescale git
SRCREV = "d35902c77a077a25e4dfedc6aac11ba49c52c586"
LOCALVERSION = "-4.0.0-wandboard"

# GPU support patches
SRC_URI += "file://drm-vivante-Add-00-sufix-in-returned-bus-Id.patch \
            file://0001-ENGR00255688-4.6.9p11.1-gpu-GPU-Kernel-driver-integr.patch \
            file://0002-ENGR00265465-gpu-Add-global-value-for-minimum-3D-clo.patch \
            file://0003-ENGR00261814-4-gpu-use-new-PU-power-on-off-interface.patch \
            file://0004-ENGR00264288-1-GPU-Integrate-4.6.9p12-release-kernel.patch \
            file://0005-ENGR00264275-GPU-Correct-suspend-resume-calling-afte.patch \
            file://0006-ENGR00265130-gpu-Correct-section-mismatch-in-gpu-ker.patch"

COMPATIBLE_MACHINE = "(wandboard)"

Is this only file that I need to modify to point to local kernel? If so what are the changes to be done

Can someone please guide me for steps to build yocto with a local kernel tar ball.

Regards,
Pavan

Alfonso Tamés

unread,
Feb 1, 2015, 2:18:56 AM2/1/15
to wand...@googlegroups.com
Hi Pavan,

It goes something like this: 

SRC_URI = "git:///home/myacct/my-kernel;protocol=file"

Good luck,

Alfonso

u2bpavankumar

unread,
Feb 1, 2015, 4:15:22 AM2/1/15
to wand...@googlegroups.com
Hi Alfonso,

As per ur SRC_URI command, it was pointing to a location in git and was trying to download from git

But my intention is to provide a reference to kernel that was locally available on my PC.

I have 3.0.35 kernel with lot of customization done to it. Now I want to give this modified kernel on my PC as reference & compile it.

Do I need to tar it and keep at some location on my PC and point SRC_URI to it? If so with what name I need to keep the tar file

Please do let me know

Regards,
Pavan

Alfonso Tamés

unread,
Feb 2, 2015, 2:37:14 AM2/2/15
to wand...@googlegroups.com
Pavan, it points to a local git repository. That's why the protocol is declared as file.

u2bpavankumar

unread,
Feb 2, 2015, 9:09:53 AM2/2/15
to wand...@googlegroups.com
Hi Alfonso,

Thanks for your reply.

I have created a local git and kept my source files inside it and added the below line to the recipe linux-wandboard.inc

SRC_URI = "git@localhost:MyProject;protocol=file"

My kernel source code is inside MyProject

Below is the error I am getting:

ERROR: ExpansionError during parsing /home/work/pavan/wandboard/yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb: Failure expanding variable do_fetch[file-checksums], expression was ${@bb.fetch.get_checksum_file_list(d)} which triggered exception MalformedUrl: The URL: 'git@localhost:MyProject;protocol=file' is invalid and cannot be interpreted

Do I need to comment out / add few other things to take from local git?

Can u please let me know what needs to be done here

Regards,
Pavan

u2bpavankumar

unread,
Feb 2, 2015, 12:33:31 PM2/2/15
to wand...@googlegroups.com
Hi,

This is the tutorial I have followed to create git repository on to my machine

https://linuxprograms.wordpress.com/2010/05/10/how-to-set-up-a-git-repository-locally/

Regards,
Pavan

u2bpavankumar

unread,
Feb 3, 2015, 2:00:28 AM2/3/15
to wand...@googlegroups.com
Hi Alfonso,

I have added the following line at $ yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard.inc

SRC_URI = "git:///localhost/MyProject.git;protocol=file"

When tried to run "bitbake core-image-minimal" below is the error I got

NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL git:///localhost/MyProject.git;protocol=file, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: repository '/localhost/MyProject.git' does not exist

ERROR: Function failed: Fetcher failure for URL: 'git:///localhost/MyProject.git;protocol=file'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:  /home/wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/log.do_fetch.4657
ERROR: Task 85 (/home/wandboard/yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb, do_fetch) failed with exit code '1'


All my kernel files are inside MyProject.git

I can cross check it by giving the following command

$ git clone git://localhost/MyProject.git

Now by doing so I can see a folder name MyProject with kernel source code

Please let me know where it is going wrong??

Regards,
Pavan

u2bpavankumar

unread,
Feb 3, 2015, 3:24:55 AM2/3/15
to wand...@googlegroups.com
I have made some progress on this.., but still does n't get compiled

I have changed the SRC_URI to

SRC_URI = "git:///home//test/new/MyProject;protocol=file;bareclone=1"

To the above location I have cloned my repository using

$ git clone git://localhost/MyProject.git

Once done, I gave bitbake core-image-minimal and below is the error

Below is the error log I have got:

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_configure (log file is located at /home/wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/log.do_configure.8798)
ERROR: Logfile of failure stored in: /home/wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/log.do_configure.8798
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'.  Stop.
| ERROR: oe_runmake failed
| WARNING: /home/wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/run.do_configure.8798:1 exit 1 from
|   oe_runmake oldconfig
| ERROR: Function failed: do_configure (log file is located at /home/wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/log.do_configure.8798)
ERROR: Task 86 (/home/wandboard/yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb, do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1556 tasks of which 1552 didn't need to be rerun and 1 failed.
No currently running tasks (1555 of 1581)

Summary: 1 task failed:
  /home/wandboard/yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb, do_configure
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.



Please let me know where it is going wrong

u2bpavankumar

unread,
Feb 3, 2015, 3:01:39 PM2/3/15
to wand...@googlegroups.com
Hi,

I have set SRC_URI as below located at $ /fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard.inc

SRC_URI = "git:///home/jos/test/temp/mykernel;protocol=file;bareclone=1"

and it started recognizing the local repo..,

Also I have modified the linux-imx file "S" parameter as below

S = "/home/jos/test/temp/mykernel"

But I ran into another error and log is mentioned below

The kernel baseline in my local repo is 3.0.35-4.1.0 and the I am using dora yocto branch

There are some set of patches I can see at linux-imx_3.0.35.bb as below


# GPU support patches
SRC_URI += "file://drm-vivante-Add-00-sufix-in-returned-bus-Id.patch \
            file://0001-ENGR00255688-4.6.9p11.1-gpu-GPU-Kernel-driver-integr.patch \
            file://0002-ENGR00265465-gpu-Add-global-value-for-minimum-3D-clo.patch \
            file://0003-ENGR00261814-4-gpu-use-new-PU-power-on-off-interface.patch \
            file://0004-ENGR00264288-1-GPU-Integrate-4.6.9p12-release-kernel.patch \
            file://0005-ENGR00264275-GPU-Correct-suspend-resume-calling-afte.patch \
            file://0006-ENGR00265130-gpu-Correct-section-mismatch-in-gpu-ker.patch"


The patch function is failing here. But with the kernel that was downloaded from git previously for wandboard is compiling with same patches with out any problem. These patches don't work for 3.0.35-4.1.0?

What should be done here to apply patch & compile the image.

please do guide me over here

Regards,
Pavan

PS: Please find the error log attached with this mail
error_log.txt

u2bpavankumar

unread,
Feb 4, 2015, 9:11:49 AM2/4/15
to wand...@googlegroups.com
Hi,

Now I am getting the following error

Any idea like "PAD_CTL_DSE_40ohm" undeclared corresponds to ??

Please do guide me

Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 uImage CC=arm-poky-linux-gnueabi-gcc  -mno-thumb-interwork -marm LD=arm-poky-linux-gnueabi-ld.bfd   LOADADDR=0x10008000
|   CHK     include/linux/version.h
|   CHK     include/generated/utsrelease.h
| make[1]: `include/generated/mach-types.h' is up to date.
|   CALL    scripts/checksyscalls.sh
|   CHK     include/generated/compile.h
|   CC      arch/arm/mach-mx6/usb_h2.o
|   CC      arch/arm/plat-mxc/devices/platform-imx-dma.o
| In file included from arch/arm/plat-mxc/include/mach/iomux-mx6q.h:25:0,
|                  from arch/arm/mach-mx6/usb_h2.c:32:
| arch/arm/mach-mx6/usb_h2.c: In function 'hsic_start':
| arch/arm/plat-mxc/include/mach/iomux-mx6q.h:83:5: error: 'PAD_CTL_DSE_40ohm' undeclared (first use in this function)
|      PAD_CTL_DSE_40ohm)
|      ^
| arch/arm/plat-mxc/include/mach/iomux-v3.h:74:44: note: in definition of macro 'MUX_PAD_CTRL'
|  #define MUX_PAD_CTRL(x)  ((iomux_v3_cfg_t)(x) << MUX_PAD_CTRL_SHIFT)
|                                             ^
| arch/arm/plat-mxc/include/mach/iomux-mx6q.h:3828:17: note: in expansion of macro 'MX6Q_USB_HSIC_PAD_CTRL'
|     MUX_PAD_CTRL(MX6Q_USB_HSIC_PAD_CTRL | PAD_CTL_PUS_47K_UP)\
|                  ^
| arch/arm/mach-mx6/usb_h2.c:180:5: note: in expansion of macro 'MX6Q_PAD_RGMII_TX_CTL__USBOH3_H2_STROBE_START'
|      MX6Q_PAD_RGMII_TX_CTL__USBOH3_H2_STROBE_START);
|      ^
| arch/arm/plat-mxc/include/mach/iomux-mx6q.h:83:5: note: each undeclared identifier is reported only once for each function it appears in
|      PAD_CTL_DSE_40ohm)
|      ^
| arch/arm/plat-mxc/include/mach/iomux-v3.h:74:44: note: in definition of macro 'MUX_PAD_CTRL'
|  #define MUX_PAD_CTRL(x)  ((iomux_v3_cfg_t)(x) << MUX_PAD_CTRL_SHIFT)
|                                             ^
| arch/arm/plat-mxc/include/mach/iomux-mx6q.h:3828:17: note: in expansion of macro 'MX6Q_USB_HSIC_PAD_CTRL'
|     MUX_PAD_CTRL(MX6Q_USB_HSIC_PAD_CTRL | PAD_CTL_PUS_47K_UP)\
|                  ^
| arch/arm/mach-mx6/usb_h2.c:180:5: note: in expansion of macro 'MX6Q_PAD_RGMII_TX_CTL__USBOH3_H2_STROBE_START'
|      MX6Q_PAD_RGMII_TX_CTL__USBOH3_H2_STROBE_START);
|      ^
| make[1]: *** [arch/arm/mach-mx6/usb_h2.o] Error 1
| make: *** [arch/arm/mach-mx6] Error 2
| make: *** Waiting for unfinished jobs....
|   CC      fs/open.o
| arch/arm/plat-mxc/devices/platform-imx-dma.c: In function 'imxXX_add_imx_dma':
| arch/arm/plat-mxc/devices/platform-imx-dma.c:265:2: error: 'imx6q_imx_sdma_data' undeclared (first use in this function)
|   imx6q_imx_sdma_data.pdata.to_version = to_version;
|   ^
| arch/arm/plat-mxc/devices/platform-imx-dma.c:265:2: note: each undeclared identifier is reported only once for each function it appears in
| arch/arm/plat-mxc/devices/platform-imx-dma.c:268:8: error: 'addr_imx6q_to1' undeclared (first use in this function)
|        &addr_imx6q_to1;
|         ^
|   CC      fs/read_write.o
| make[2]: *** [arch/arm/plat-mxc/devices/platform-imx-dma.o] Error 1
| make[1]: *** [arch/arm/plat-mxc/devices] Error 2
| make: *** [arch/arm/plat-mxc] Error 2
|   CC      fs/file_table.o
|   CC      fs/super.o
|   CC      fs/char_dev.o
|   CC      fs/stat.o
|   CC      fs/exec.o
|   CC      fs/pipe.o
|   CC      fs/namei.o
|   CC      fs/fcntl.o
|   CC      fs/ioctl.o
|   CC      fs/readdir.o
|   CC      fs/select.o
|   CC      fs/fifo.o
|   CC      fs/dcache.o
|   CC      fs/inode.o
|   CC      fs/attr.o
|   CC      fs/bad_inode.o
|   CC      fs/file.o
|   CC      fs/filesystems.o
|   CC      fs/namespace.o
|   CC      fs/seq_file.o
|   CC      fs/xattr.o
|   CC      fs/libfs.o
|   CC      fs/fs-writeback.o
|   CC      fs/pnode.o
|   CC      fs/drop_caches.o
|   CC      fs/splice.o
|   CC      fs/sync.o
|   CC      fs/utimes.o
|   CC      fs/stack.o
|   CC      fs/fs_struct.o
|   CC      fs/statfs.o
|   CC      fs/buffer.o
|   CC      fs/bio.o
|   CC      fs/block_dev.o
|   CC      fs/direct-io.o
|   CC      fs/mpage.o
|   CC      fs/ioprio.o
|   CC      fs/devpts/inode.o
|   LD      fs/devpts/devpts.o
|   LD      fs/devpts/built-in.o
|   CC      fs/ext4/balloc.o
|   CC      fs/fat/cache.o
|   CC      fs/jbd2/transaction.o
|   CC      fs/fuse/dev.o
|   CC      fs/fat/dir.o
|   CC      fs/ext4/bitmap.o
|   CC      fs/ext4/dir.o
|   CC      fs/jbd2/commit.o
|   CC      fs/ext4/file.o
|   CC      fs/fuse/dir.o
|   CC      fs/fat/fatent.o
|   CC      fs/ext4/fsync.o
|   CC      fs/jbd2/recovery.o
| In file included from fs/ext4/fsync.c:33:0:
| fs/ext4/ext4_jbd2.h: In function 'ext4_inode_journal_mode':
| fs/ext4/ext4_jbd2.h:288:1: warning: control reaches end of non-void function [-Wreturn-type]
|  }
|  ^
|   CC      fs/ext4/ialloc.o
|   CC      fs/fat/file.o
|   CC      fs/fuse/file.o
|   CC      fs/jbd2/checkpoint.o
| In file included from include/linux/mm.h:11:0,
|                  from fs/fuse/fuse_i.h:18,
|                  from fs/fuse/file.c:9:
| fs/fuse/file.c: In function 'fuse_file_poll':
| include/linux/rbtree.h:171:26: warning: 'parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
|   node->rb_parent_color = (unsigned long )parent;
|                           ^
| fs/fuse/file.c:2052:27: note: 'parent' was declared here
|    struct rb_node **link, *parent;
|                            ^
|   CC      fs/fat/inode.o
|   CC      fs/jbd2/revoke.o
|   CC      fs/ext4/inode.o
|   CC      fs/jbd2/journal.o
| In file included from fs/ext4/inode.c:46:0:
| fs/ext4/ext4_jbd2.h: In function 'ext4_inode_journal_mode':
| fs/ext4/ext4_jbd2.h:288:1: warning: control reaches end of non-void function [-Wreturn-type]
|  }
|  ^
|   CC      fs/fuse/inode.o
|   CC      fs/fat/misc.o
|   CC      fs/fat/namei_vfat.o
|   CC      fs/fuse/control.o
|   LD      fs/fuse/fuse.o
|   LD      fs/jbd2/jbd2.o
|   LD      fs/fuse/built-in.o
|   LD      fs/jbd2/built-in.o
|   CC      fs/nls/nls_base.o
|   CC      fs/notify/fsnotify.o
|   LD      fs/fat/fat.o
|   LD      fs/fat/vfat.o
|   LD      fs/fat/built-in.o
|   CC      fs/partitions/check.o
|   CC      fs/nls/nls_cp437.o
|   CC      fs/notify/notification.o
|   CC      fs/ext4/page-io.o
|   CC      fs/nls/nls_ascii.o
|   CC      fs/nls/nls_iso8859-1.o
|   CC      fs/notify/group.o
|   CC      fs/ext4/ioctl.o
|   CC      fs/nls/nls_utf8.o
|   LD      fs/nls/built-in.o
|   CC      fs/partitions/msdos.o
|   CC      fs/proc/mmu.o
|   CC      fs/notify/inode_mark.o
|   CC      fs/ext4/namei.o
|   CC      fs/proc/task_mmu.o
|   CC      fs/partitions/efi.o
|   CC      fs/notify/mark.o
|   CC      fs/proc/inode.o
|   LD      fs/partitions/built-in.o
|   CC      fs/notify/vfsmount_mark.o
|   LD      fs/quota/built-in.o
|   CC      fs/proc/root.o
|   CC      fs/ramfs/inode.o
|   LD      fs/notify/dnotify/built-in.o
|   LD      fs/notify/fanotify/built-in.o
|   CC      fs/notify/inotify/inotify_fsnotify.o
|   CC      fs/proc/base.o
|   CC      fs/ramfs/file-mmu.o
|   CC      fs/ext4/super.o
|   LD      fs/ramfs/ramfs.o
|   LD      fs/ramfs/built-in.o
|   CC      fs/notify/inotify/inotify_user.o
|   CC      fs/sysfs/inode.o
|   CC      fs/sysfs/file.o
|   LD      fs/notify/inotify/built-in.o
|   LD      fs/notify/built-in.o
|   CC      fs/eventpoll.o
|   CC      fs/proc/generic.o
|   CC      fs/sysfs/dir.o
| fs/sysfs/dir.c:414:14: warning: 'sysfs_pathname' defined but not used [-Wunused-function]
|  static char *sysfs_pathname(struct sysfs_dirent *sd, char *path)
|               ^
|   CC      fs/anon_inodes.o
|   CC      fs/sysfs/symlink.o
|   CC      fs/proc/array.o
|   CC      fs/signalfd.o
|   CC      fs/ext4/symlink.o
|   CC      fs/ext4/hash.o
|   CC      fs/sysfs/mount.o
|   CC      fs/proc/proc_tty.o
|   CC      fs/timerfd.o
|   CC      fs/proc/cmdline.o
|   CC      fs/ext4/resize.o
|   CC      fs/sysfs/bin.o
|   CC      fs/proc/consoles.o
|   CC      fs/proc/cpuinfo.o
|   CC      fs/proc/devices.o
|   CC      fs/eventfd.o
|   CC      fs/sysfs/group.o
|   CC      fs/proc/interrupts.o
|   CC      fs/ext4/extents.o
|   LD      fs/sysfs/built-in.o
|   CC      fs/proc/loadavg.o
|   CC      fs/locks.o
|   CC      fs/binfmt_script.o
| In file included from fs/ext4/extents.c:44:0:
| fs/ext4/ext4_jbd2.h: In function 'ext4_inode_journal_mode':
| fs/ext4/ext4_jbd2.h:288:1: warning: control reaches end of non-void function [-Wreturn-type]
|  }
|  ^
|   CC      fs/proc/meminfo.o
|   CC      fs/binfmt_elf.o
|   CC      fs/proc/stat.o
|   CC      fs/proc/uptime.o
|   CC      fs/mbcache.o
|   CC      fs/proc/version.o
|   CC      fs/proc/softirqs.o
|   CC      fs/proc/namespaces.o
|   CC      fs/proc/proc_sysctl.o
|   CC      fs/ext4/ext4_jbd2.o
|   CC      fs/proc/proc_net.o
|   CC      fs/ext4/migrate.o
| In file included from fs/ext4/ext4_jbd2.c:5:0:
| fs/ext4/ext4_jbd2.h: In function 'ext4_inode_journal_mode':
| fs/ext4/ext4_jbd2.h:288:1: warning: control reaches end of non-void function [-Wreturn-type]
|  }
|  ^
|   CC      fs/proc/kmsg.o
|   CC      fs/ext4/mballoc.o
|   CC      fs/ext4/block_validity.o
|   LD      fs/proc/proc.o
|   LD      fs/proc/built-in.o
|   CC      fs/ext4/move_extent.o
|   CC      fs/ext4/mmp.o
| In file included from fs/ext4/mballoc.h:22:0,
|                  from fs/ext4/mballoc.c:24:
| fs/ext4/ext4_jbd2.h: In function 'ext4_inode_journal_mode':
| fs/ext4/ext4_jbd2.h:288:1: warning: control reaches end of non-void function [-Wreturn-type]
|  }
|  ^
|   CC      fs/ext4/xattr.o
|   CC      fs/ext4/xattr_user.o
|   CC      fs/ext4/xattr_trusted.o
|   LD      fs/ext4/ext4.o
|   LD      fs/ext4/built-in.o
|   LD      fs/built-in.o
| ERROR: oe_runmake failed
| WARNING: /home/srikanth/Desktop/work/pavan//wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/run.do_compile.6787:1 exit 1 from
|   exit 1
| ERROR: Function failed: do_compile (log file is located at /home/srikanth/Desktop/work/pavan//wandboard/yocto/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/temp/log.do_compile.6787)
ERROR: Task 6 (/home/srikanth/Desktop/work/pavan//wandboard/yocto/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard_3.0.35.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 555 tasks of which 554 didn't need to be rerun and 1 failed.
No currently running tasks (355 of 568)

John Weber

unread,
Feb 24, 2015, 10:52:39 AM2/24/15
to wand...@googlegroups.com

On 2/3/15 2:01 PM, u2bpavankumar wrote:
> Hi,
>
> I have set SRC_URI as below located at $
> /fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard.inc
>
> SRC_URI = "git:///home/jos/test/temp/mykernel;protocol=file;bareclone=1"
>
> and it started recognizing the local repo..,
>
> Also I have modified the linux-imx file "S" parameter as below
>
> S = "/home/jos/test/temp/mykernel"
>
> But I ran into another error and log is mentioned below
>
> The kernel baseline in my local repo is 3.0.35-4.1.0 and the I am using dora
> yocto branch

>
> There are some set of patches I can see at linux-imx_3.0.35.bb as below
>
> # GPU support patches
> SRC_URI += "file://drm-vivante-Add-00-sufix-in-returned-bus-Id.patch \
> file://0001-ENGR00255688-4.6.9p11.1-gpu-GPU-Kernel-driver-integr.patch \
> file://0002-ENGR00265465-gpu-Add-global-value-for-minimum-3D-clo.patch \
> file://0003-ENGR00261814-4-gpu-use-new-PU-power-on-off-interface.patch \
> file://0004-ENGR00264288-1-GPU-Integrate-4.6.9p12-release-kernel.patch \
> file://0005-ENGR00264275-GPU-Correct-suspend-resume-calling-afte.patch \
> file://0006-ENGR00265130-gpu-Correct-section-mismatch-in-gpu-ker.patch"
>
>
> The patch function is failing here. But with the kernel that was downloaded
> from git previously for wandboard is compiling with same patches with out any
> problem. These patches don't work for 3.0.35-4.1.0?
The patches above may not apply to 3.0.35_4.1.0 kernel since we basically
skipped this rev in the Yocto community. Why don't you look at Daisy or Dizzy,
which use 3.10? Or master, currently on 3.10.53?
>
> What should be done here to apply patch & compile the image.
>
> please do guide me over here
>
> Regards,
> Pavan

It seems that what you're wanting to do is to use a local kernel repository in a
Yocto build.

There are a lot of ways to do this (building your own recipe is one), but
normally when I'm working on a Wandboard kernel I'll just do this in
build/conf/local.conf:

WANDBOARD_GITHUB_MIRROR = "git:///opt/git/linux.git" <-- your local git
repository here
SRCBRANCH_pn-linux-wandboard = "wandboard_imx_3.10.17_1.0.1_ga_test" <-- the
branch
SRCREV_pn-linux-wandboard = "d9652cfe075fce42596119f761e2240d7721e477" <-- the
commit hash

We added these variables to the Wandboard kernel recipe some time ago (I think
before 1.6 released, not sure) to allow anyone (but basically community kernel
maintainers) to easily swap in a local repository/branch for the Wandboard
kernel when building images.

What I would do is to build Yocto Daisy, Dizzy, or Master using the default
recipes. Then clone the Wandboard linux kernel locally and check out the branch
noted in the kernel recipe, then make your changes on top of that.

John


Reply all
Reply to author
Forward
0 new messages