* kernels
@ 2011-07-15 13:21 Phil Blundell
2011-07-15 13:51 ` kernels Bruce Ashfield
0 siblings, 1 reply; 11+ messages in thread
From: Phil Blundell @ 2011-07-15 13:21 UTC (permalink / raw)
To: oe-core
The other day I was working on a BSP layer for a fairly generic i586
system and I was struck by the fact that we don't appear to have any
vanilla kernel recipes in oe-core. I had sort of expected that, to get
a standard bzImage out, I would just need to ship an appropriate
defconfig in my layer and everything else would "just work".
However, the only kernel that I could immediately find in oe-core was
linux-yocto, which appears to be somewhat more specialized than that
and, at a first glance, looks like it would be better placed in some or
other poky layer than oe-core itself.
Is it the intent that BSP layers are meant to start from linux-yocto and
customise that, or are they expected to provide their own standalone
recipes?
I was also slightly confused by the fragmentary nature of the kernel
helper files. Chasing the references from linux-yocto.bb seems to show
that it includes two .incs and explicitly inherits a total of
six .bbclasses (one of which is, admittedly, blank) and it's not always
entirely obvious what each one is really doing or how they are meant to
interact with each other.
p.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-15 13:21 kernels Phil Blundell
@ 2011-07-15 13:51 ` Bruce Ashfield
2011-07-15 15:02 ` kernels Phil Blundell
0 siblings, 1 reply; 11+ messages in thread
From: Bruce Ashfield @ 2011-07-15 13:51 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
> The other day I was working on a BSP layer for a fairly generic i586
> system and I was struck by the fact that we don't appear to have any
> vanilla kernel recipes in oe-core. I had sort of expected that, to get
> a standard bzImage out, I would just need to ship an appropriate
> defconfig in my layer and everything else would "just work".
Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
kernel base can work in this mode, since that was a design goal of
1.0.
You pick a branch, throw in a config fragment (or defconfig if you really
want) and build. The base branches in the tree are generic enough to
sort a range of boards out of the box, and should form a base.
The benefit with this is that you'd pickup and fixes, features and benefit
from the QA and testing that is performed on that kernel. Everyone
doing their own thing, means duplicated efforts.
>
> However, the only kernel that I could immediately find in oe-core was
> linux-yocto, which appears to be somewhat more specialized than that
> and, at a first glance, looks like it would be better placed in some or
> other poky layer than oe-core itself.
We use linux-yocto to support the set of embedded features and work
flow that yocto is intended to support, but as I said above, it is intended
to be used either standalone (i.e. without oe/poky/bitbake) or as an
extension point.
>
> Is it the intent that BSP layers are meant to start from linux-yocto and
> customise that, or are they expected to provide their own standalone
> recipes?
Customization is what we do, or you can include and extend. I have
2 extension recipes in the poky-extras repo that do just that.
>
> I was also slightly confused by the fragmentary nature of the kernel
> helper files. Chasing the references from linux-yocto.bb seems to show
> that it includes two .incs and explicitly inherits a total of
> six .bbclasses (one of which is, admittedly, blank) and it's not always
> entirely obvious what each one is really doing or how they are meant to
> interact with each other.
The factoring of these files was to pull out common parts, so the recipe
could be re-used and extended. Nothing is ever perfect, so it is still a
work in progress. The empty .inc looks to be a casualty of cleanups and
we didn't drop the bogus include in linux-yocto, that's some house keeping
that I'll take care of.
I can show you what you need to do, and generate some docs around this
(if you are interested) and if there are problems, we'll fix the workflow.
Cheers,
Bruce
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-15 13:51 ` kernels Bruce Ashfield
@ 2011-07-15 15:02 ` Phil Blundell
2011-07-15 15:36 ` kernels Bruce Ashfield
0 siblings, 1 reply; 11+ messages in thread
From: Phil Blundell @ 2011-07-15 15:02 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
> > The other day I was working on a BSP layer for a fairly generic i586
> > system and I was struck by the fact that we don't appear to have any
> > vanilla kernel recipes in oe-core. I had sort of expected that, to get
> > a standard bzImage out, I would just need to ship an appropriate
> > defconfig in my layer and everything else would "just work".
>
> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
> kernel base can work in this mode, since that was a design goal of
> 1.0.
>
> You pick a branch, throw in a config fragment (or defconfig if you really
> want) and build. The base branches in the tree are generic enough to
> sort a range of boards out of the box, and should form a base.
Okay, cool. I'll give it a go and see how I get on.
Is there a description anywhere of what the functional differences are
between the code in linux-yocto git and the upstream kernel.org tree?
p.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-15 15:02 ` kernels Phil Blundell
@ 2011-07-15 15:36 ` Bruce Ashfield
2011-07-20 15:42 ` kernels Bruce Ashfield
0 siblings, 1 reply; 11+ messages in thread
From: Bruce Ashfield @ 2011-07-15 15:36 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>> > The other day I was working on a BSP layer for a fairly generic i586
>> > system and I was struck by the fact that we don't appear to have any
>> > vanilla kernel recipes in oe-core. I had sort of expected that, to get
>> > a standard bzImage out, I would just need to ship an appropriate
>> > defconfig in my layer and everything else would "just work".
>>
>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>> kernel base can work in this mode, since that was a design goal of
>> 1.0.
>>
>> You pick a branch, throw in a config fragment (or defconfig if you really
>> want) and build. The base branches in the tree are generic enough to
>> sort a range of boards out of the box, and should form a base.
>
> Okay, cool. I'll give it a go and see how I get on.
>
> Is there a description anywhere of what the functional differences are
> between the code in linux-yocto git and the upstream kernel.org tree?
It varies, and the variables are many, so I can answer this in several ways.
Here's some bullet points to save anyone from reading an essay:
- The ultimate source is obviously the upstream kernel. The goal is
no patches, or
are the very least, no changes that are carried for a significant
amount of time.
This typically holds for BSPs, drivers, bug fixes, etc. But sometimes not for
features or other out of tree projects that haven't made it as
viable upstream
features (yet .. or ever).
So all that says is that "We aren't trying to vary it wildly, but
create an infrastructure
where interesting projects can be tried out, and to allow others to
vary it wildly if they
want"
- The linux-yocto tree, once a branch is checked out and a build is
started, is just
like any other kernel tree. There are plenty of other examples of
trees with multiple
branches for containing and controlling development. The
difference here could be
that the branch is found and checked out by the build process
(that's the more
'complex' mode, but you can just build 'whatever branch the repo
is on' as well)
- To see the actual differences from the upstream base, there are tags and the
branches themselves, which all facilitate using git to dump logs
and changes from
the merge base of the core branches (i.e. yocto/base).
- The features you'll find in the tree change by kernel version
(since some projects
may lag their updates and hence miss a tree or two), timing of the mainline
kernel, the invasiveness of a feature or simply what is being
worked on by some
yocto (or other) developers!
Hope that helps,
Bruce
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-15 15:36 ` kernels Bruce Ashfield
@ 2011-07-20 15:42 ` Bruce Ashfield
2011-07-20 15:45 ` kernels Koen Kooi
0 siblings, 1 reply; 11+ messages in thread
From: Bruce Ashfield @ 2011-07-20 15:42 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>> > The other day I was working on a BSP layer for a fairly generic i586
>>> > system and I was struck by the fact that we don't appear to have any
>>> > vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>> > a standard bzImage out, I would just need to ship an appropriate
>>> > defconfig in my layer and everything else would "just work".
>>>
>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>> kernel base can work in this mode, since that was a design goal of
>>> 1.0.
>>>
>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>> want) and build. The base branches in the tree are generic enough to
>>> sort a range of boards out of the box, and should form a base.
>>
>> Okay, cool. I'll give it a go and see how I get on.
>>
>> Is there a description anywhere of what the functional differences are
>> between the code in linux-yocto git and the upstream kernel.org tree?
>
> It varies, and the variables are many, so I can answer this in several ways.
Following up on my own email. I'm just about to push out the 3.0
kernel support / changes, so I'm seeing the light at the end of the tunnel
and recalled that this is still hanging a bit.
Is there anything tangible you wanted me to do here ? Create an example ?
Write a short howto .. or something else ?
Cheers,
Bruce
>
> Here's some bullet points to save anyone from reading an essay:
>
> - The ultimate source is obviously the upstream kernel. The goal is
> no patches, or
> are the very least, no changes that are carried for a significant
> amount of time.
> This typically holds for BSPs, drivers, bug fixes, etc. But sometimes not for
> features or other out of tree projects that haven't made it as
> viable upstream
> features (yet .. or ever).
>
> So all that says is that "We aren't trying to vary it wildly, but
> create an infrastructure
> where interesting projects can be tried out, and to allow others to
> vary it wildly if they
> want"
>
> - The linux-yocto tree, once a branch is checked out and a build is
> started, is just
> like any other kernel tree. There are plenty of other examples of
> trees with multiple
> branches for containing and controlling development. The
> difference here could be
> that the branch is found and checked out by the build process
> (that's the more
> 'complex' mode, but you can just build 'whatever branch the repo
> is on' as well)
>
> - To see the actual differences from the upstream base, there are tags and the
> branches themselves, which all facilitate using git to dump logs
> and changes from
> the merge base of the core branches (i.e. yocto/base).
>
> - The features you'll find in the tree change by kernel version
> (since some projects
> may lag their updates and hence miss a tree or two), timing of the mainline
> kernel, the invasiveness of a feature or simply what is being
> worked on by some
> yocto (or other) developers!
>
> Hope that helps,
>
> Bruce
>
>
>
>>
>> p.
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-20 15:42 ` kernels Bruce Ashfield
@ 2011-07-20 15:45 ` Koen Kooi
2011-07-20 19:47 ` kernels Bruce Ashfield
0 siblings, 1 reply; 11+ messages in thread
From: Koen Kooi @ 2011-07-20 15:45 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>> system and I was struck by the fact that we don't appear to have any
>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>> defconfig in my layer and everything else would "just work".
>>>>
>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>> kernel base can work in this mode, since that was a design goal of
>>>> 1.0.
>>>>
>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>> want) and build. The base branches in the tree are generic enough to
>>>> sort a range of boards out of the box, and should form a base.
>>>
>>> Okay, cool. I'll give it a go and see how I get on.
>>>
>>> Is there a description anywhere of what the functional differences are
>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>
>> It varies, and the variables are many, so I can answer this in several ways.
>
> Following up on my own email. I'm just about to push out the 3.0
> kernel support / changes, so I'm seeing the light at the end of the tunnel
> and recalled that this is still hanging a bit.
>
> Is there anything tangible you wanted me to do here ? Create an example ?
> Write a short howto .. or something else ?
A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-20 15:45 ` kernels Koen Kooi
@ 2011-07-20 19:47 ` Bruce Ashfield
2011-07-21 17:23 ` kernels Anders Darander
0 siblings, 1 reply; 11+ messages in thread
From: Bruce Ashfield @ 2011-07-20 19:47 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Wed, Jul 20, 2011 at 11:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>
> Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
>
>> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
>> <bruce.ashfield@gmail.com> wrote:
>>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>>> system and I was struck by the fact that we don't appear to have any
>>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>>> defconfig in my layer and everything else would "just work".
>>>>>
>>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>>> kernel base can work in this mode, since that was a design goal of
>>>>> 1.0.
>>>>>
>>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>>> want) and build. The base branches in the tree are generic enough to
>>>>> sort a range of boards out of the box, and should form a base.
>>>>
>>>> Okay, cool. I'll give it a go and see how I get on.
>>>>
>>>> Is there a description anywhere of what the functional differences are
>>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>>
>>> It varies, and the variables are many, so I can answer this in several ways.
>>
>> Following up on my own email. I'm just about to push out the 3.0
>> kernel support / changes, so I'm seeing the light at the end of the tunnel
>> and recalled that this is still hanging a bit.
>>
>> Is there anything tangible you wanted me to do here ? Create an example ?
>> Write a short howto .. or something else ?
>
> A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
That's reasonable. Once I get the imminent kernel uprev out the door, I'll
focus on something along these lines.
Bruce
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-20 19:47 ` kernels Bruce Ashfield
@ 2011-07-21 17:23 ` Anders Darander
2011-07-21 17:36 ` kernels Bruce Ashfield
0 siblings, 1 reply; 11+ messages in thread
From: Anders Darander @ 2011-07-21 17:23 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On 20 jul 2011, at 22:18, "Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:
> On Wed, Jul 20, 2011 at 11:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>
>> Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
>>
>>> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
>>> <bruce.ashfield@gmail.com> wrote:
>>>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>>>> system and I was struck by the fact that we don't appear to have any
>>>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>>>> defconfig in my layer and everything else would "just work".
>>>>>>
>>>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>>>> kernel base can work in this mode, since that was a design goal of
>>>>>> 1.0.
>>>>>>
>>>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>>>> want) and build. The base branches in the tree are generic enough to
>>>>>> sort a range of boards out of the box, and should form a base.
>>>>>
>>>>> Okay, cool. I'll give it a go and see how I get on.
>>>>>
>>>>> Is there a description anywhere of what the functional differences are
>>>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>>>
>>>> It varies, and the variables are many, so I can answer this in several ways.
>>>
>>> Following up on my own email. I'm just about to push out the 3.0
>>> kernel support / changes, so I'm seeing the light at the end of the tunnel
>>> and recalled that this is still hanging a bit.
>>>
>>> Is there anything tangible you wanted me to do here ? Create an example ?
>>> Write a short howto .. or something else ?
>>
>> A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
>
> That's reasonable. Once I get the imminent kernel uprev out the door, I'll
> focus on something along these lines.
That sounds good. Upon re-reading the email, I wasn't really sure if the intent was a guide on how to supply your own configuration, or whether it was intended to be about how to integrate a custom BSP-kernel (preferably both tarball and directly from a local git repo). If it was the first, then I hope that later on we'll be able to derive a guide for developing a custom BSP-layer (it's the kernel part I'm interested in).
Preferably first a guide on how to get a custom BSP kernel built from git, and later on, when there both are time available as well as some more stabilization, how to base my own BSP kernel on linux-yocto (eg. using linux-yocto as the upstream repo). It's unfortunately not always that likely that the BSP for some products will be mainlined...
Cheers,
Anders
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-21 17:23 ` kernels Anders Darander
@ 2011-07-21 17:36 ` Bruce Ashfield
2011-07-21 20:28 ` kernels Anders Darander
2011-08-15 20:52 ` kernels Bruce Ashfield
0 siblings, 2 replies; 11+ messages in thread
From: Bruce Ashfield @ 2011-07-21 17:36 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Thu, Jul 21, 2011 at 1:23 PM, Anders Darander <anders@chargestorm.se> wrote:
>
> On 20 jul 2011, at 22:18, "Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:
>
>> On Wed, Jul 20, 2011 at 11:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>
>>> Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
>>>
>>>> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
>>>> <bruce.ashfield@gmail.com> wrote:
>>>>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>>>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>>>>> system and I was struck by the fact that we don't appear to have any
>>>>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>>>>> defconfig in my layer and everything else would "just work".
>>>>>>>
>>>>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>>>>> kernel base can work in this mode, since that was a design goal of
>>>>>>> 1.0.
>>>>>>>
>>>>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>>>>> want) and build. The base branches in the tree are generic enough to
>>>>>>> sort a range of boards out of the box, and should form a base.
>>>>>>
>>>>>> Okay, cool. I'll give it a go and see how I get on.
>>>>>>
>>>>>> Is there a description anywhere of what the functional differences are
>>>>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>>>>
>>>>> It varies, and the variables are many, so I can answer this in several ways.
>>>>
>>>> Following up on my own email. I'm just about to push out the 3.0
>>>> kernel support / changes, so I'm seeing the light at the end of the tunnel
>>>> and recalled that this is still hanging a bit.
>>>>
>>>> Is there anything tangible you wanted me to do here ? Create an example ?
>>>> Write a short howto .. or something else ?
>>>
>>> A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
>>
>> That's reasonable. Once I get the imminent kernel uprev out the door, I'll
>> focus on something along these lines.
>
> That sounds good. Upon re-reading the email, I wasn't really sure if the intent was a guide on how to supply your own configuration, or whether it was intended to be about how to integrate a custom BSP-kernel (preferably both tarball and directly from a local git repo). If it was the first, then I hope that later on we'll be able to derive a guide for developing a custom BSP-layer (it's the kernel part I'm interested in).
It was more the first in this case, but it can actually encompass the
second. What would be covered here would be a special case of developing
a custom layer. Taking some arbitrary source, configuration, patches, git trees
and creating a kernel repo that would work with the linux-yocto tools and
recipes.
The second topic of creating a custom BSP layer, doesn't (and shouldn't
normally) have to go so far. A simple branch reference, or reference to
a tree based on a known linux-yocto is all you need to build with linux-yocto
for most custom BSPs. As for the source of that custom BSP (tarball or
git) that would be covered in how to create that custom branch reference.
>
> Preferably first a guide on how to get a custom BSP kernel built from git, and later on, when there both are time available as well as some more stabilization, how to base my own BSP kernel on linux-yocto (eg. using linux-yocto as the upstream repo). It's unfortunately not always that likely that the BSP for some products will be mainlined...
I experience this every day as well .. bsp patches that will largely
live forever, so
I completely understand. The structure of the repos is created to manage just
this sort of nagging patch and any crimes they may have committed. So this
topic can be explicitly called out and worked on.
The basics are covered in the existing guides, but it sounds like some end
to end use cases might be in order.
Bruce
>
> Cheers,
> Anders
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-21 17:36 ` kernels Bruce Ashfield
@ 2011-07-21 20:28 ` Anders Darander
2011-08-15 20:52 ` kernels Bruce Ashfield
1 sibling, 0 replies; 11+ messages in thread
From: Anders Darander @ 2011-07-21 20:28 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On 21 jul 2011, at 19:36, "Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:
> On Thu, Jul 21, 2011 at 1:23 PM, Anders Darander <anders@chargestorm.se> wrote:
>>
>> On 20 jul 2011, at 22:18, "Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:
>>
>>> On Wed, Jul 20, 2011 at 11:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>>
>>>> Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
>>>>
>>>>> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
>>>>> <bruce.ashfield@gmail.com> wrote:
>>>>>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>>>>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>>>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>>>>>> system and I was struck by the fact that we don't appear to have any
>>>>>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>>>>>> defconfig in my layer and everything else would "just work".
>>>>>>>>
>>>>>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>>>>>> kernel base can work in this mode, since that was a design goal of
>>>>>>>> 1.0.
>>>>>>>>
>>>>>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>>>>>> want) and build. The base branches in the tree are generic enough to
>>>>>>>> sort a range of boards out of the box, and should form a base.
>>>>>>>
>>>>>>> Okay, cool. I'll give it a go and see how I get on.
>>>>>>>
>>>>>>> Is there a description anywhere of what the functional differences are
>>>>>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>>>>>
>>>>>> It varies, and the variables are many, so I can answer this in several ways.
>>>>>
>>>>> Following up on my own email. I'm just about to push out the 3.0
>>>>> kernel support / changes, so I'm seeing the light at the end of the tunnel
>>>>> and recalled that this is still hanging a bit.
>>>>>
>>>>> Is there anything tangible you wanted me to do here ? Create an example ?
>>>>> Write a short howto .. or something else ?
>>>>
>>>> A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
>>>
>>> That's reasonable. Once I get the imminent kernel uprev out the door, I'll
>>> focus on something along these lines.
>>
>> That sounds good. Upon re-reading the email, I wasn't really sure if the intent was a guide on how to supply your own configuration, or whether it was intended to be about how to integrate a custom BSP-kernel (preferably both tarball and directly from a local git repo). If it was the first, then I hope that later on we'll be able to derive a guide for developing a custom BSP-layer (it's the kernel part I'm interested in).
>
> It was more the first in this case, but it can actually encompass the
> second. What would be covered here would be a special case of developing
> a custom layer. Taking some arbitrary source, configuration, patches, git trees
> and creating a kernel repo that would work with the linux-yocto tools and
> recipes.
>
> The second topic of creating a custom BSP layer, doesn't (and shouldn't
> normally) have to go so far. A simple branch reference, or reference to
> a tree based on a known linux-yocto is all you need to build with linux-yocto
> for most custom BSPs. As for the source of that custom BSP (tarball or
> git) that would be covered in how to create that custom branch reference.
>
>>
>> Preferably first a guide on how to get a custom BSP kernel built from git, and later on, when there both are time available as well as some more stabilization, how to base my own BSP kernel on linux-yocto (eg. using linux-yocto as the upstream repo). It's unfortunately not always that likely that the BSP for some products will be mainlined...
>
> I experience this every day as well .. bsp patches that will largely
> live forever, so
> I completely understand. The structure of the repos is created to manage just
> this sort of nagging patch and any crimes they may have committed. So this
> topic can be explicitly called out and worked on.
>
> The basics are covered in the existing guides, but it sounds like some end
> to end use cases might be in order.
Sounds good.
I'll try to have a new look at the existing guides in a few weeks, but I guess that some end-to-end use cases would be helpful. Not least when it comes to try to combine a custom git repo based both on a custom BSP and linux-yocto (at least trying to sync it up to linux-yocto).
I guess that I'm not alone in that I've not yet converted our old Linux recipes from oe-dev to be based on Linux-yocto (otoh, our developers are still working on our oe-dev based tree), so I'm not in a real hurry.
Cheers,
Anders
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernels
2011-07-21 17:36 ` kernels Bruce Ashfield
2011-07-21 20:28 ` kernels Anders Darander
@ 2011-08-15 20:52 ` Bruce Ashfield
1 sibling, 0 replies; 11+ messages in thread
From: Bruce Ashfield @ 2011-08-15 20:52 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Thu, Jul 21, 2011 at 1:36 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Thu, Jul 21, 2011 at 1:23 PM, Anders Darander <anders@chargestorm.se> wrote:
>>
>> On 20 jul 2011, at 22:18, "Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:
>>
>>> On Wed, Jul 20, 2011 at 11:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>>
>>>> Op 20 jul 2011, om 17:42 heeft Bruce Ashfield het volgende geschreven:
>>>>
>>>>> On Fri, Jul 15, 2011 at 11:36 AM, Bruce Ashfield
>>>>> <bruce.ashfield@gmail.com> wrote:
>>>>>> On Fri, Jul 15, 2011 at 11:02 AM, Phil Blundell <philb@gnu.org> wrote:
>>>>>>> On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
>>>>>>>> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
>>>>>>>>> The other day I was working on a BSP layer for a fairly generic i586
>>>>>>>>> system and I was struck by the fact that we don't appear to have any
>>>>>>>>> vanilla kernel recipes in oe-core. I had sort of expected that, to get
>>>>>>>>> a standard bzImage out, I would just need to ship an appropriate
>>>>>>>>> defconfig in my layer and everything else would "just work".
>>>>>>>>
>>>>>>>> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
>>>>>>>> kernel base can work in this mode, since that was a design goal of
>>>>>>>> 1.0.
>>>>>>>>
>>>>>>>> You pick a branch, throw in a config fragment (or defconfig if you really
>>>>>>>> want) and build. The base branches in the tree are generic enough to
>>>>>>>> sort a range of boards out of the box, and should form a base.
>>>>>>>
>>>>>>> Okay, cool. I'll give it a go and see how I get on.
>>>>>>>
>>>>>>> Is there a description anywhere of what the functional differences are
>>>>>>> between the code in linux-yocto git and the upstream kernel.org tree?
>>>>>>
>>>>>> It varies, and the variables are many, so I can answer this in several ways.
>>>>>
>>>>> Following up on my own email. I'm just about to push out the 3.0
>>>>> kernel support / changes, so I'm seeing the light at the end of the tunnel
>>>>> and recalled that this is still hanging a bit.
>>>>>
>>>>> Is there anything tangible you wanted me to do here ? Create an example ?
>>>>> Write a short howto .. or something else ?
>>>>
>>>> A guide to make your own setup that isn't based on linux-yocto but which does work with the linux-yocto bbclass?
>>>
>>> That's reasonable. Once I get the imminent kernel uprev out the door, I'll
>>> focus on something along these lines.
>>
>> That sounds good. Upon re-reading the email, I wasn't really sure if the intent was a guide on how to supply your own configuration, or whether it was intended to be about how to integrate a custom BSP-kernel (preferably both tarball and directly from a local git repo). If it was the first, then I hope that later on we'll be able to derive a guide for developing a custom BSP-layer (it's the kernel part I'm interested in).
>
> It was more the first in this case, but it can actually encompass the
> second. What would be covered here would be a special case of developing
> a custom layer. Taking some arbitrary source, configuration, patches, git trees
> and creating a kernel repo that would work with the linux-yocto tools and
> recipes.
>
> The second topic of creating a custom BSP layer, doesn't (and shouldn't
> normally) have to go so far. A simple branch reference, or reference to
> a tree based on a known linux-yocto is all you need to build with linux-yocto
> for most custom BSPs. As for the source of that custom BSP (tarball or
> git) that would be covered in how to create that custom branch reference.
bumping this old thread (by replying to myself), this hasn't been forgotten,
and I spent considerable time on some docs last week. I've got a few small
sections remaining to complete (but important sections), and I'll have some
reasonable docs that I can send out in the next day or so.
Cheers,
Bruce
>
>>
>> Preferably first a guide on how to get a custom BSP kernel built from git, and later on, when there both are time available as well as some more stabilization, how to base my own BSP kernel on linux-yocto (eg. using linux-yocto as the upstream repo). It's unfortunately not always that likely that the BSP for some products will be mainlined...
>
> I experience this every day as well .. bsp patches that will largely
> live forever, so
> I completely understand. The structure of the repos is created to manage just
> this sort of nagging patch and any crimes they may have committed. So this
> topic can be explicitly called out and worked on.
>
> The basics are covered in the existing guides, but it sounds like some end
> to end use cases might be in order.
>
> Bruce
>
>>
>> Cheers,
>> Anders
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2011-08-15 20:57 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-15 13:21 kernels Phil Blundell
2011-07-15 13:51 ` kernels Bruce Ashfield
2011-07-15 15:02 ` kernels Phil Blundell
2011-07-15 15:36 ` kernels Bruce Ashfield
2011-07-20 15:42 ` kernels Bruce Ashfield
2011-07-20 15:45 ` kernels Koen Kooi
2011-07-20 19:47 ` kernels Bruce Ashfield
2011-07-21 17:23 ` kernels Anders Darander
2011-07-21 17:36 ` kernels Bruce Ashfield
2011-07-21 20:28 ` kernels Anders Darander
2011-08-15 20:52 ` kernels Bruce Ashfield
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox