On Wed, Nov 4, 2015 at 6:14 PM, Jian Liu <jian....@windriver.com> wrote: > Hi, > > All kernels I list bellow will perform do_fetch(), do_unpack(), > do_kernel_checkout(). > do_unpack() will put a bare git repo under WORKDIR and then > do_kernel_checkout() > will move the bare repo to bitbake/tmp/work-share/<board > name>/kernel-source(value of variable S), > then performing "git checkout". > > So do_ar_original must wait until do_kernel_checkout() is completed and then > make tarball using the code under S. > Do I make that clear? > > > You refer to kernels other than linux-yocto. Can you give me an example? > I do not know how to build such kernel.
Add another BSP layer e.g. meta-raspberrypi to your bblayers.conf and then MACHINE=raspberrypi2 and see what you are trying to do still holds. > > Thanks! > Jian > > > On 2015年11月04日 13:57, Khem Raj wrote: >>> >>> On Nov 3, 2015, at 1:22 AM, Jian Liu<jian....@windriver.com> wrote: >>> > >>> >Hi, >>> > >>> >I test linux-dummy linux-yocto-dev linux-yocto-rt linux-yocto-tiny and >>> > the result is as follows, >>> > >>> >linux-dummy: this package just meets some dependency and there is no >>> > source code for it. >>> > The patch does not impact it >>> >linux-yocto, linux-yocto-dev, linux-yocto-rt, linux-yocto-tiny: The S >>> > variable of all packages is set to STAGING_KERNEK_DIR. >>> > do_fetch and do_unpack just leave a bare git repo >>> > of kernel and do_kernel_checkout gets the source code >>> > >> >> does it cover the case when kernel is not linux-yocto was basic question, >> I am not clear if thats covered in any of above >> >>> >Thanks! > > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
