[yocto] Build the kernel for I.mx6 board

[vinod kumar]

Hi Ronaldo,

Thanks for your reply and valuable suggestions.

*But cleansstate work the same way as cleanal*l. It means it also remove
the kernel source code from build directory.

However the link which you share with me is very nice, I go through it but
also does not give the idea.

I have the follows queries:


   -  I want to clean my kernel directory(*.o binary file only* not .c
   file) only. So is there any way to do that?


   - And one more thing how we can *apply the patch in kernel driver* (eg.
   USB driver) and add the customize configuration from source directory.
   Please give an example, if it is possible.




On Sun, Aug 10, 2014 at 9:46 PM, Ronaldo Nunez <ronaldo.viera at gmail.com>
wrote:

> Hello Vinod!
>
> Cleanall command deletes all releated to the tasks on your recipe,
> including the source code. You should try cleansstate command.
>
> Take a look to this doc,
>
> https://www.yoctoproject.org/sites/yoctoproject.org/files/kernel-lab-1.4.pdf
>
> It's releated to kernel development using Yocto Project, I think it will
> help you a lot.
>
> Cheers,
>
> Ronaldo
>
>
> 2014-08-10 3:16 GMT-03:00 vinod kumar <vinodmaverickr007 at gmail.com>:
>
>> Hi,
>>
>> I have build the yocto for I.mx6 board. After building the source code,
>> kernel is in build directory. So when I run
>> bitbake linux-imx -c cleanall, it remove the entire kernel source code.
>>
>> So I have some queries:
>> 1) Is it possible to modify(to made changes) the kernel source code
>> directly from source directory, without going into build directory.
>>
>> 2) How can I remove the compiled file(.o) file from the kernel source
>> code, without deleting the entire kernel source code.
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
>
> --
> Ronaldo Nunez
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20140811/581fe980/attachment.html>