Magic kernel config option.
Quoted 6 lines · Bruce Ashfield
Quoted 2 lines · Brian Smucker
Hi,
Catching up on email from the holidays. Did you ever get an answer to this ?
Not yet, resumed my quest today.
Quoted 18 lines
Quoted 8 lines
I'm a yocto mostly-newbie, trying to find my way. I have a custom layer that I am using to build a kernel. The layer right now consists of a few kernel patches and a defconfig and is based on the standard kernel otherwise.
When I do a diff on my defconfig and the bitbake generated .config, they are quite similar, but the
CONFIG_UNION_FS=yline magically shows up. I'm wondering where it comes from and how to disable it.
CONFIG_UNION_FSis being enabled by the standard kernel (and all kernels that inherit it). Since you are based on that kernel, you get the option enabled.Quoted 4 lines
I can do a bitbake -c menuconfig virtual/kernel and eliminate that option giving me the kernel I want, but those changes are gone after a bitbake -c cleansstate ...
Quoted 6 lines
Have you tried putting
#
CONFIG_UNION_FSis not setin your defconfig ? That should disable it.
I did try that, but that did not disable it.
So after much pain and thrashing about to figure things out, now I see that in the standard-nocfg.scc file, the unionfs feature is set. This file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-cache/ktypes/standard/ directory.
My current burning question is: Where is does this file come from? It does not seem to be part of the kernel git repository. I can changes this file and affect the kernel build, but again, those changes are transitory and do not persist after cleaning.
Thanks,
Brian
Quoted 30 lines · Brian Smucker
Quoted 6 lines · Bruce Ashfield
Quoted 2 lines · Brian Smucker
Hi,
Catching up on email from the holidays. Did you ever get an answer to this ?
Not yet, resumed my quest today.
Quoted 1 line
Quoted 1 line
I'm a yocto mostly-newbie, trying to find my way. I have a custom
layer
Quoted 1 line
Quoted 1 line
that I am using to build a kernel. The layer right now consists of a
few
Quoted 4 lines
Quoted 4 lines
kernel patches and a defconfig and is based on the standard kernel otherwise.
When I do a diff on my defconfig and the bitbake generated .config,
they
Quoted 12 lines
Quoted 2 lines
are quite similar, but the
CONFIG_UNION_FS=yline magically shows up. I'm wondering where it comes from and how to disable it.
CONFIG_UNION_FSis being enabled by the standard kernel (and all kernels that inherit it). Since you are based on that kernel, you get the option enabled.Quoted 4 lines
I can do a bitbake -c menuconfig virtual/kernel and eliminate that option giving me the kernel I want, but those changes are gone after a bitbake -c cleansstate ...
Quoted 7 lines
Quoted 6 lines
Have you tried putting
#
CONFIG_UNION_FSis not setin your defconfig ? That should disable it.
I did try that, but that did not disable it.
Hmmm. It worked here. I'll run another test shortly (I'm working on 3.8-rc1 at the moment).
Quoted 10 lines
So after much pain and thrashing about to figure things out, now I see that in the standard-nocfg.scc file, the unionfs feature is set. This file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-cache/ktypes/standard/ directory.
My current burning question is: Where is does this file come from? It does not seem to be part of the kernel git repository. I can changes this file and affect the kernel build, but again, those changes are transitory and do not persist after cleaning.
It's from the meta branch of the kernel git repository. Those are all the fragments that are used to construct and configure the kernel. Part of the build process makes them available to the configuration phase.
As something else to try, call your file <foo>.cfg and add it to the SRC_URI the same way you added the defconfig. defconfig's get special processing, calling it <foo>.cfg will simply get your changes added to the end of the build and they teka precedence. That being said, if a feature with a Kconfig of the kernel has a "select UNIONFS" then you can't override it with a config/defconfig option, you need to patch the kernel.
If you send me your defconfig, I can run some test builds here.
Bruce
Quoted 6 lines
Thanks,
Brian
Quoted 60 lines · Bruce Ashfield
Quoted 32 lines · Brian Smucker
Quoted 6 lines · Bruce Ashfield
Quoted 2 lines · Brian Smucker
Hi,
Catching up on email from the holidays. Did you ever get an answer to this ?
Not yet, resumed my quest today.
Quoted 1 line
Quoted 1 line
I'm a yocto mostly-newbie, trying to find my way. I have a custom
layer
Quoted 1 line
Quoted 1 line
that I am using to build a kernel. The layer right now consists of a
few
Quoted 4 lines
Quoted 4 lines
kernel patches and a defconfig and is based on the standard kernel otherwise.
When I do a diff on my defconfig and the bitbake generated .config,
they
Quoted 1 line
Quoted 1 line
are quite similar, but the
CONFIG_UNION_FS=yline magically showsup.
Quoted 9 lines
Quoted 1 line
I'm wondering where it comes from and how to disable it.
CONFIG_UNION_FSis being enabled by the standard kernel (and all kernels that inherit it). Since you are based on that kernel, you get the option enabled.Quoted 3 lines
I can do a bitbake -c menuconfig virtual/kernel and eliminate that option giving me the kernel I want, but those changes are gone
after a
Quoted 2 lines
Quoted 1 line
bitbake -c cleansstate ...
Quoted 7 lines
Quoted 6 lines
Have you tried putting
#
CONFIG_UNION_FSis not setin your defconfig ? That should disable it.
I did try that, but that did not disable it.
Hmmm. It worked here. I'll run another test shortly (I'm working on 3.8-rc1 at the moment).
Quoted 10 lines
So after much pain and thrashing about to figure things out, now I see that in the standard-nocfg.scc file, the unionfs feature is set. This file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-cache/ktypes/standard/ directory.
My current burning question is: Where is does this file come from? It does not seem to be part of the kernel git repository. I can changes this file and affect the kernel build, but again, those changes are transitory and do not persist after cleaning.
It's from the meta branch of the kernel git repository. Those are all the fragments that are used to construct and configure the kernel. Part of the build process makes them available to the configuration phase.
Quoted 4 lines
As something else to try, call your file <foo>.cfg and add it to the
SRC_URIthe same way you added the defconfig. defconfig's get special processing, calling it <foo>.cfg will simply get your changes added to the end of the build and they teka precedence.
Tried your above suggestion, didn't seem to work.
So with a bit of further testing it looks like by the time the defconfig and the <foo>.cfg are copied into the linux directory, the commented out config option: # CONFIG_UNION_FS is not set line is totally gone.
Quoted 4 lines
That being said, if
a feature with aKconfigof the kernel has a "select UNIONFS" then you can't override it with a config/defconfig option, you need to patch the kernel.
Not sure what you are saying here. If you mean that the unionfs kernel option is required by another selected kernel config option, I'm pretty sure that's not the case. I can bitbake -c menuconfig virtual/kernel and merely deselect the unionfs option and the kernel is good.
Brian
Quoted 14 lines
If you send me your defconfig, I can run some test builds here.
Bruce
Quoted 6 lines
Thanks,
Brian
Quoted 70 lines · Brian Smucker
Quoted 62 lines · Bruce Ashfield
Quoted 31 lines · Brian Smucker
Quoted 6 lines · Bruce Ashfield
Quoted 2 lines · Brian Smucker
Hi,
Catching up on email from the holidays. Did you ever get an answer to this ?
Not yet, resumed my quest today.
Quoted 1 line
Quoted 1 line
I'm a yocto mostly-newbie, trying to find my way. I have a custom
layer
Quoted 1 line
Quoted 1 line
that I am using to build a kernel. The layer right now consists of a
few
Quoted 4 lines
Quoted 4 lines
kernel patches and a defconfig and is based on the standard kernel otherwise.
When I do a diff on my defconfig and the bitbake generated .config,
they
Quoted 10 lines
Quoted 2 lines
are quite similar, but the
CONFIG_UNION_FS=yline magically shows up. I'm wondering where it comes from and how to disable it.
CONFIG_UNION_FSis being enabled by the standard kernel (and all kernels that inherit it). Since you are based on that kernel, you get the option enabled.Quoted 3 lines
I can do a bitbake -c menuconfig virtual/kernel and eliminate that option giving me the kernel I want, but those changes are gone after
a
Quoted 2 lines
Quoted 1 line
bitbake -c cleansstate ...
Quoted 8 lines
Quoted 6 lines
Have you tried putting
#
CONFIG_UNION_FSis not setin your defconfig ? That should disable it.
I did try that, but that did not disable it.
Hmmm. It worked here. I'll run another test shortly (I'm working on 3.8-rc1 at the moment).
Quoted 10 lines
So after much pain and thrashing about to figure things out, now I see that in the standard-nocfg.scc file, the unionfs feature is set. This file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-**cache/ktypes/standard/ directory.
My current burning question is: Where is does this file come from? It does not seem to be part of the kernel git repository. I can changes this file and affect the kernel build, but again, those changes are transitory and do not persist after cleaning.
It's from the meta branch of the kernel git repository. Those are all the fragments that are used to construct and configure the kernel. Part of the build process makes them available to the configuration phase.
Quoted 5 lines
As something else to try, call your file <foo>.cfg and add it to the
SRC_URIthe same way you added the defconfig. defconfig's get special processing, calling it <foo>.cfg will simply get your changes added to the end of the build and they teka precedence.
Quoted 8 lines
Tried your above suggestion, didn't seem to work.
So with a bit of further testing it looks like by the time the defconfig and the <foo>.cfg are copied into the linux directory, the commented out config option: #
CONFIG_UNION_FSis not set
line is totally gone.
Interesting .. and not really possible if you are talking about the version in $WORKDIR (i.e
the directory above the linux/ source directory). Those are straight copies from your
layer, with zero processing. Same with the copy within the linux/meta/cfg/* directory
structure, they are straight copies and are only processed after being ordered and
concatenated.
Quoted 13 lines
That being said, if
Quoted 4 lines
a feature with a
Kconfigof the kernel has a "select UNIONFS" then you can't override it with a config/defconfig option, you need to patch the kernel.Not sure what you are saying here. If you mean that the unionfs kernel option is required by another selected kernel config option, I'm pretty sure that's not the case. I can bitbake -c menuconfig virtual/kernel and merely deselect the unionfs option and the kernel is good.
I can't see your source tree, so it was always an option. I know it definitely isn't
the case in the linux-yocto tree. But the ability to deselect it in menuconfig isn't
contingent on something else not selecting it from within another Kconfig.
Again, if you send me your defconfig and local.conf changes (for the BSP), I'll
run a kernel configuration test and be able to easily tell you what is happening.
Cheers,
Bruce
Quoted 27 lines
Brian
If you send me your defconfig, I can run some test builds here.
Quoted 14 lines
Bruce
Quoted 6 lines
Thanks,
Brian
______________________________**_________________
yocto mailing list
[email protected]
https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
I take everything back. The entry in the defconfig did the trick. My problem was that the recipe was grabbing its defconfig from the wrong directory, costing me much confusion.
So sorry for the false alarm. Thanks again for your help. When you said the defconfig was a straight copy, the light finally dawned that there was something else going on.
The silver lining to all this thrashing around for me was the fact that I do understand the kernel bitbake process much better.
Brian
Quoted 166 lines · Bruce Ashfield
On Wed, Jan 2, 2013 at 4:47 PM, Brian Smucker <[email protected] <mailto:[email protected]>> wrote:
On 1/2/2013 1:12 PM, Bruce Ashfield wrote:
On 13-01-02 04:11 PM, Brian Smucker wrote:
On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
> On 12-12-24 02:59 PM, Brian Smucker wrote:
>> Hi,
>>
>
> Catching up on email from the holidays. Did you ever
get an answer
> to this ?
Not yet, resumed my quest today.>> I'm a yocto mostly-newbie, trying to find my way. I
have a custom
layer
>> that I am using to build a kernel. The layer right now
consists of a
few
>> kernel patches and a defconfig and is based on the
standard kernel
>> otherwise.
>>
>> When I do a diff on my defconfig and the bitbake
generated .config,
they
>> are quite similar, but theCONFIG_UNION_FS=yline
magically shows up.
>> I'm wondering where it comes from and how to disable it. >
>CONFIG_UNION_FSis being enabled by the standard kernel
(and all
> kernels that inherit it). Since you are based on that
kernel, you
> get the option enabled.
>
>>
>> I can do a bitbake -c menuconfig virtual/kernel and
eliminate that
>> option giving me the kernel I want, but those changes
are gone after a
>> bitbake -c cleansstate ...
>
> Have you tried putting
>
> #CONFIG_UNION_FSis not set
>
> in your defconfig ? That should disable it.
>
I did try that, but that did not disable it.Hmmm. It worked here. I'll run another test shortly (I'm working on
3.8-rc1 at the moment).So after much pain and thrashing about to figure things out, now I see
that in the standard-nocfg.scc file, the unionfs feature is set. This
file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-cache/ktypes/standard/ directory.My current burning question is: Where is does this file come from? It
does not seem to be part of the kernel git repository. I can changes
this file and affect the kernel build, but again, those changes are
transitory and do not persist after cleaning.It's from the meta branch of the kernel git repository. Those are all the fragments that are used to construct and configure the kernel. Part of the build process makes them available to the configuration phase.
As something else to try, call your file <foo>.cfg and add it to the
SRC_URIthe same way you added the defconfig. defconfig's get special
processing, calling it <foo>.cfg will simply get your changes added
to the end of the build and they teka precedence.Tried your above suggestion, didn't seem to work.
So with a bit of further testing it looks like by the time the defconfig and the <foo>.cfg are copied into the linux directory, the commented out config option: #
CONFIG_UNION_FSis not set line is totally gone.Interesting .. and not really possible if you are talking about the version in $WORKDIR (i.e the directory above the linux/ source directory). Those are straight copies from your layer, with zero processing. Same with the copy within the linux/meta/cfg/* directory structure, they are straight copies and are only processed after being ordered and concatenated.
That being said, if
a feature with aKconfigof the kernel has a "select UNIONFS" then you
can't override it with a config/defconfig option, you need to patch
the kernel.Not sure what you are saying here. If you mean that the unionfs kernel option is required by another selected kernel config option, I'm pretty sure that's not the case. I can bitbake -c menuconfig virtual/kernel and merely deselect the unionfs option and the kernel is good.
I can't see your source tree, so it was always an option. I know it definitely isn't the case in the linux-yocto tree. But the ability to deselect it in menuconfig isn't contingent on something else not selecting it from within another
Kconfig.Again, if you send me your defconfig and local.conf changes (for the BSP), I'll run a kernel configuration test and be able to easily tell you what is happening.
Cheers,
Bruce
Brian
If you send me your defconfig, I can run some test builds here.
Bruce
Thanks,
Brian
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yoctoSignature · 1 line
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 7 lines · Brian Smucker
I take everything back. The entry in the defconfig did the trick. My problem was that the recipe was grabbing its defconfig from the wrong directory, costing me much confusion.
So sorry for the false alarm. Thanks again for your help. When you said the defconfig was a straight copy, the light finally dawned that there was something else going on.
Aha! That is good news. Thanks for following up.
Quoted 3 lines
The silver lining to all this thrashing around for me was the fact that I do understand the kernel bitbake process much better.
:) Always a good thing.
Bruce
Quoted 187 lines
Brian
Quoted 173 lines · Bruce Ashfield
On Wed, Jan 2, 2013 at 4:47 PM, Brian Smucker <[email protected] <mailto:[email protected]>> wrote:
On 1/2/2013 1:12 PM, Bruce Ashfield wrote:
On 13-01-02 04:11 PM, Brian Smucker wrote:
On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
> On 12-12-24 02:59 PM, Brian Smucker wrote:
>> Hi,
>>
>
> Catching up on email from the holidays. Did you ever get an answer
> to this ?
Not yet, resumed my quest today.>> I'm a yocto mostly-newbie, trying to find my way. I have a custom
layer
>> that I am using to build a kernel. The layer right now consists of a
few
>> kernel patches and a defconfig and is based on the standard kernel
>> otherwise.
>>
>> When I do a diff on my defconfig and the bitbake generated .config,
they
>> are quite similar, but theCONFIG_UNION_FS=yline magically shows up.
>> I'm wondering where it comes from and how to disable it. >
>CONFIG_UNION_FSis being enabled by the standard kernel (and all
> kernels that inherit it). Since you are based on that kernel, you
> get the option enabled.
>
>>
>> I can do a bitbake -c menuconfig virtual/kernel and eliminate that
>> option giving me the kernel I want, but those changes are gone after a
>> bitbake -c cleansstate ...
>
> Have you tried putting
>
> #CONFIG_UNION_FSis not set
>
> in your defconfig ? That should disable it.
>
I did try that, but that did not disable it.Hmmm. It worked here. I'll run another test shortly (I'm working on
3.8-rc1 at the moment).So after much pain and thrashing about to figure things out, now I see
that in the standard-nocfg.scc file, the unionfs feature is set. This
file is found in the following path: tmp/work/.. ../linux/meta/cfg/kernel-cache/ktypes/standard/ directory.My current burning question is: Where is does this file come from? It
does not seem to be part of the kernel git repository. I can changes
this file and affect the kernel build, but again, those changes are
transitory and do not persist after cleaning.It's from the meta branch of the kernel git repository. Those are all the fragments that are used to construct and configure the kernel. Part of the build process makes them available to the configuration phase.
As something else to try, call your file <foo>.cfg and add it to the
SRC_URIthe same way you added the defconfig. defconfig's get special
processing, calling it <foo>.cfg will simply get your changes added
to the end of the build and they teka precedence.Tried your above suggestion, didn't seem to work.
So with a bit of further testing it looks like by the time the defconfig and the <foo>.cfg are copied into the linux directory, the commented out config option: #
CONFIG_UNION_FSis not set line is totally gone.Interesting .. and not really possible if you are talking about the version in $WORKDIR (i.e
the directory above the linux/ source directory). Those are straight copies from your
layer, with zero processing. Same with the copy within the linux/meta/cfg/* directory
structure, they are straight copies and are only processed after being ordered and
concatenated.That being said, if
a feature with aKconfigof the kernel has a "select UNIONFS" then you
can't override it with a config/defconfig option, you need to patch
the kernel.Not sure what you are saying here. If you mean that the unionfs kernel option is required by another selected kernel config option, I'm pretty sure that's not the case. I can bitbake -c menuconfig virtual/kernel and merely deselect the unionfs option and the kernel is good.
I can't see your source tree, so it was always an option. I know it definitely isn't
the case in the linux-yocto tree. But the ability to deselect it in menuconfig isn't
contingent on something else not selecting it from within anotherKconfig.Again, if you send me your defconfig and local.conf changes (for the BSP), I'll
run a kernel configuration test and be able to easily tell you what is happening.Cheers,
Bruce
Brian
If you send me your defconfig, I can run some test builds here.
Bruce
Thanks,
Brian
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yoctoQuoted 3 lines
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto