How to work with linux-yocto kernel


Elvis Dowson
 

Hi,
     I just don't understand how to work with the linux-yocto kernel.

For example, I created a local copy of the yocto kernel, and updated the linux-yocto_3.8.bb recipe to point to the local copy (git:///<path>;protocol=file, etc)

Then I created a local branch meta, and another local branch standard/qemuarma9 and then updated the machine definitions in the meta branch for qemuarma9.

When I run yocto, and bitbake linux-yocto, in the tmp folder, if I check the git branch, it's checked out standard/common-pc/atom-pc.

This is really weird.

I've wasted a couple of days because the yocto build infrastructure was checkout out the wrong branch. 

Elvis Dowson


Bruce Ashfield <bruce.ashfield@...>
 

On 13-08-28 01:48 PM, Elvis Dowson wrote:
Hi,
I just don't understand how to work with the linux-yocto kernel.

For example, I created a local copy of the yocto kernel, and updated the
linux-yocto_3.8.bb recipe to point to the local copy
(git:///<path>;protocol=file, etc)

Then I created a local branch meta, and another local branch
standard/qemuarma9 and then updated the machine definitions in the meta
branch for qemuarma9.

When I run yocto, and bitbake linux-yocto, in the tmp folder, if I check
the git branch, it's checked out *_standard/common-pc/atom-pc._*
There were some old bugs which caused the wrong board description to
be picked up, the seems similar.

But without seeing your exact changes, as they sit in the tree, I
can't be sure.

Did you also update the meta and machine branch SRCREVs ?


This is really weird.

I've wasted a couple of days because the yocto build infrastructure was
checkout out the wrong branch.
Start with the yocto-bsp tool, it's probably the easiest way to define a
new BSP in recipe space, and then move it to the kernel later.

Cheers,

Bruce


Elvis Dowson


_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Elvis Dowson
 

Hi Bruce,

On Aug 28, 2013, at 9:52 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

There were some old bugs which caused the wrong board description to
be picked up, the seems similar.

But without seeing your exact changes, as they sit in the tree, I
can't be sure.

Did you also update the meta and machine branch SRCREVs ?
No, I didn't.

I've just done this now. It's only after you mentioned it
that I noticed the SRCREV_meta variable in linux-yocto_3.8.bb

While obvious, once stated, it's better to explicitly document
this step in the kernel development guide, so that people remember to
do it:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html

BTW, in qemuarma9-standard.scc, for the branch, do I specify
standard/qemuarma9 or just qemuarma9 ?

Best regards,

Elvis Dowson


Bruce Ashfield <bruce.ashfield@...>
 

On 13-08-28 02:05 PM, Elvis Dowson wrote:
Hi Bruce,

On Aug 28, 2013, at 9:52 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

There were some old bugs which caused the wrong board description to
be picked up, the seems similar.

But without seeing your exact changes, as they sit in the tree, I
can't be sure.

Did you also update the meta and machine branch SRCREVs ?
No, I didn't.

I've just done this now. It's only after you mentioned it
that I noticed the SRCREV_meta variable in linux-yocto_3.8.bb

While obvious, once stated, it's better to explicitly document
this step in the kernel development guide, so that people remember to
do it:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html
If you have a moment, drop a quick bugzilla and we can make sure
that happens.


BTW, in qemuarma9-standard.scc, for the branch, do I specify
standard/qemuarma9 or just qemuarma9 ?
Just qemuarma9. Branch names are automatically built up with inheritance.

So if you include other features that branch (like the standard
kernel), your name is appended. That frees your individual feature
from needing to know where it sits in the include order.

Cheers,

Bruce


Best regards,

Elvis Dowson


Elvis Dowson
 

On Aug 28, 2013, at 10:07 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

On 13-08-28 02:05 PM, Elvis Dowson wrote:
Hi Bruce,

On Aug 28, 2013, at 9:52 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

There were some old bugs which caused the wrong board description to
be picked up, the seems similar.

But without seeing your exact changes, as they sit in the tree, I
can't be sure.

Did you also update the meta and machine branch SRCREVs ?
No, I didn't.

I've just done this now. It's only after you mentioned it
that I noticed the SRCREV_meta variable in linux-yocto_3.8.bb

While obvious, once stated, it's better to explicitly document
this step in the kernel development guide, so that people remember to
do it:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html
If you have a moment, drop a quick bugzilla and we can make sure
that happens.
I've just done this now.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5065

Best regards,

Elvis Dowson


Darren Hart <dvhart@...>
 

On Wed, 2013-08-28 at 22:22 +0400, Elvis Dowson wrote:
On Aug 28, 2013, at 10:07 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

On 13-08-28 02:05 PM, Elvis Dowson wrote:
Hi Bruce,

On Aug 28, 2013, at 9:52 PM, Bruce Ashfield <bruce.ashfield@...> wrote:

There were some old bugs which caused the wrong board description to
be picked up, the seems similar.

But without seeing your exact changes, as they sit in the tree, I
can't be sure.

Did you also update the meta and machine branch SRCREVs ?
No, I didn't.

I've just done this now. It's only after you mentioned it
that I noticed the SRCREV_meta variable in linux-yocto_3.8.bb

While obvious, once stated, it's better to explicitly document
this step in the kernel development guide, so that people remember to
do it:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html
If you have a moment, drop a quick bugzilla and we can make sure
that happens.
I've just done this now.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5065
Thank you for taking the time to file the bug. This is crucial feedback
and the only way for the documentation to improve is for people like you
to review and provide feedback. Thank you!

Please follow the bug as we may have questions for you to make sure we
address the issue.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel