kernel-dev: Updates "Generating Configuration Files" section
PATCH 1/1 kernel-dev: Updates "Generating Configuration Files" section
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
--- documentation/kernel-dev/kernel-dev-common.xml | 25 +++++++++---------------- 1 file changed, 9 insertions(+), 16 deletions(-)
documentation/kernel-dev/kernel-dev-common.xml +9 -16
@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the <filename>menuconfig</filename> command: <literallayout class='monospaced'> $ bitbake linux-yocto -c menuconfig </literallayout></para></listitem> - <listitem><para>Prepare a configuration fragment based on - the differences between the two files. - </para></listitem> + <listitem><para>Run the <filename>diffconfig</filename> + command to prepare a configuration fragment. + The result file <filename>fragment.cfg</filename> will be placed in + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}</filename> directory: + <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs to be a + The <filename>diffconfig</filename> command creates a file that is a list of Linux kernel <filename>CONFIG_</filename> assignments. - It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan on reviewing - the output as you can usually remove some of the defaults: - <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<link linkend='changing-the-configuration'>Changing the Configuration</link>" section for information on how to use the output as a configuration fragment.
Signature · 1 line
1.8.3.2
Quoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>
Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R. as the next obvious owner).
Scott, This is good stuff to add. My only thought is this is new functionality, the old method is still valid - and necessary before 1.6. What are your thoughts on dealing with this? Does the manual with 1.6 ONLY apply to 1.6?
--
Darren
Quoted 71 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result file<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulinkQuoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +4
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs to be a + The <filename>diffconfig</filename> command creates afile that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.Signature · 6 lines
1.8.3.2 _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center
Yes - the manual for 1.6 is only for that release. I would have to take separate steps to apply it to dora or Dylan branches.
Quoted 112 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; [email protected]
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R. as the next obvious owner).
Scott, This is good stuff to add. My only thought is this is new functionality, the old method is still valid - and necessary before 1.6.
What are your thoughts on dealing with this? Does the manual with 1.6 ONLY apply to 1.6?--
DarrenQuoted 32 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result fileQuoted 3 lines
<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ul
Quoted 32 lines
ink
Quoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +4
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs to be a + The <filename>diffconfig</filename> command creates afile that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.
--
1.8.3.2Quoted 5 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
Quoted 2 lines · Scott M
Yes - the manual for 1.6 is only for that release. I would have to take separate steps to apply it to dora or Dylan branches.
The point there being that someone reading the current manual and working on the 1.5 releases, would find these proposed changes will fail. The method being removed here would work on all versions since this document was created.
--
Darren
Quoted 119 lines
Quoted 117 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; [email protected]
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R.
as the next obvious owner).Scott, This is good stuff to add. My only thought is this is new functionality, the
old method is still valid - and necessary before 1.6.
What are your thoughts on dealing with this? Does the manual with 1.6 ONLY
apply to 1.6?--
DarrenQuoted 32 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result fileQuoted 3 lines
<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ul
Quoted 33 lines
ink
Quoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +3
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs tobe a
+ The <filename>diffconfig</filename> command creates a
file that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.
--
1.8.3.2Quoted 5 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
Signature · 3 lines
Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center
What you are saying is that the current method works for pre-1.6. And, the proposed changes from the patch apply only to 1.6 and on. I would apply the patch only to the "latest" version of the docs, which is the tip of master and will be for 1.6.
Scott
Quoted 151 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas; [email protected]
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 2 lines · Scott M
Yes - the manual for 1.6 is only for that release. I would have to take separate steps to apply it to dora or Dylan branches.
The point there being that someone reading the current manual and working on the 1.5 releases, would find these proposed changes will fail. The method being removed here would work on all versions since this document was created.
--
DarrenQuoted 111 lines
Quoted 111 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; [email protected]
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R.
as the next obvious owner).Scott, This is good stuff to add. My only thought is this is new functionality, the old method is still valid - and necessary before 1.6.
What are your thoughts on dealing with this? Does the manual with 1.6 ONLY apply to 1.6?--
DarrenQuoted 32 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result fileQuoted 3 lines
<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ul
Quoted 39 lines
ink
Quoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +3
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs tobe a
+ The <filename>diffconfig</filename> command creates
+ a
file that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.
--
1.8.3.2_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoQuoted 9 lines
Quoted 7 lines
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
Quoted 4 lines · Scott M
What you are saying is that the current method works for pre-1.6. And, the proposed changes from the patch apply only to 1.6 and on. I would apply the patch only to the "latest" version of the docs, which is the tip of master and will be for 1.6.
OK. My hesitation/question here is about the expectation of the document. If someone is working on the 1.5 release, should they ONLY use the 1.5 documentation? Does this mean you "backport" fixes from the current development docs back to the previous releases of the docs?
--
Darren
Quoted 158 lines
Scott
Quoted 153 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas; [email protected]
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 2 lines · Scott M
Yes - the manual for 1.6 is only for that release. I would have to take separate steps to apply it to dora or Dylan branches.
The point there being that someone reading the current manual and working on the 1.5 releases, would find these proposed changes will fail. The method
being removed here would work on all versions since this document was created.--
DarrenQuoted 112 lines
Quoted 112 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; [email protected]
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R.
as the next obvious owner).Scott, This is good stuff to add. My only thought is this is new functionality, the old method is still valid - and necessary before 1.6.
What are your thoughts on dealing with this? Does the manual with 1.6 ONLY apply to 1.6?--
DarrenQuoted 32 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result fileQuoted 3 lines
<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ul
Quoted 40 lines
ink
Quoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +3
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs tobe a
+ The <filename>diffconfig</filename> command creates
+ a
file that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.
--
1.8.3.2_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoQuoted 9 lines
Quoted 7 lines
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
Signature · 3 lines
Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center
Darren,
The way I work is if a change applies to a previous major release, then I cherry-pick the change onto the top of the branch for the previously released version. Otherwise, the change goes onto the top of master only, which will be the case for this change. Regarding your specific question... if someone is working on/using a specific version of YP, they should use the documentation for that version. So someone using 1.5 needs to use 1.5 version of the manuals and not 1.6 or 1.5.1.
Scott
Quoted 190 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 5:48 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas; [email protected]
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 4 lines · Scott M
What you are saying is that the current method works for pre-1.6. And, the proposed changes from the patch apply only to 1.6 and on. I would apply the patch only to the "latest" version of the docs, which is the tip of master and will be for 1.6.
OK. My hesitation/question here is about the expectation of the document. If someone is working on the 1.5 release, should they ONLY use the 1.5 documentation? Does this mean you "backport" fixes from the current development docs back to the previous releases of the docs?
--
DarrenQuoted 157 lines
Scott
Quoted 152 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas; [email protected]
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 2 lines · Scott M
Yes - the manual for 1.6 is only for that release. I would have to take separate steps to apply it to dora or Dylan branches.
The point there being that someone reading the current manual and working on the 1.5 releases, would find these proposed changes will fail. The method being removed here would work on all versions since this document was created.
--
DarrenQuoted 112 lines
Quoted 112 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; [email protected]
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" sectionQuoted 6 lines · João Henrique Ferreira de Freitas
Add a new step about how to use diffconfig task to create kernel config fragments.
[YOCTO #3862]
Signed-off-by João Henrique Ferreira de Freitas <[email protected]>Thank you for updating the documentation. Please Cc: the relevant parties with patches to the list (the author for one, and a git log would reveal Scott R.
as the next obvious owner).Scott, This is good stuff to add. My only thought is this is new functionality, the old method is still valid - and necessary before 1.6.
What are your thoughts on dealing with this? Does the manual with 1.6 ONLY apply to 1.6?--
DarrenQuoted 32 lines
---
documentation/kernel-dev/kernel-dev-common.xml| 25
+++++++++----------------1 file changed, 9 insertions(+), 16 deletions(-)documentation/kernel-dev/kernel-dev-common.xml +0
-4@@ -342,32 +342,25 @@ <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f </literallayout></para></listitem> - <listitem><para>Copy and rename the resulting - <filename>.config</filename> file (e.g. - <filename>config.orig</filename>). - </para></listitem> <listitem><para>Run the<filename>menuconfig</filename>
command:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout></para></listitem>
- <listitem><para>Prepare a configuration fragment
based ondocumentation/kernel-dev/kernel-dev-common.xml +1
-2- the differences between the two files. - </para></listitem> + <listitem><para>Run the<filename>diffconfig</filename>
documentation/kernel-dev/kernel-dev-common.xml +2
-0+ command to prepare a configuration fragment. + The result fileQuoted 3 lines
<filename>fragment.cfg</filename> will be placed in
+ <filename>${</filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ul
Quoted 40 lines
ink
Quoted 1 line
<filename>}</filename> directory:
documentation/kernel-dev/kernel-dev-common.xml +3
-1+ <literallayout class='monospaced'> + $ bitbake linux-yocto -c diffconfig + </literallayout></para></listitem> </orderedlist> </para> <para> - Ultimately, the configuration fragment file needs tobe a
+ The <filename>diffconfig</filename> command
+ creates a
file that is a
list of Linux kernel <filename>CONFIG_</filename>
assignments.documentation/kernel-dev/kernel-dev-common.xml +0
-4- It cannot be in <filename>diff</filename> format. - Here is an example of a command that creates your - configuration fragment file. - Regardless of the exact command you use, plan onreviewing
- the output as you can usually remove some of the
defaults:documentation/kernel-dev/kernel-dev-common.xml +1
-3- <literallayout class='monospaced'> - $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg - </literallayout> + See the "<linklinkend='changing-the-configuration'>Changing the Configuration</link>"
section for information on how to use the output as a configuration fragment.
--
1.8.3.2_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoQuoted 9 lines
Quoted 7 lines
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center