Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
On 3/5/14, 18:20, João Henrique Ferreira de Freitas joa...@gmail.com
wrote:
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 joa...@gmail.com
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
---
documentation/kernel-dev/kernel-dev-common.xml | 25
+
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the
filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment
based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the
filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file
filenamefragment.cfg/filename will be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-WORKDIR'filenameWORKDIR/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 filenamediffconfig/filename command creates a
file that is a
list of Linux kernel filenameCONFIG_/filename
assignments.
-It cannot be in filenamediff/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.
--
1.8.3.2
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
On 3/10/14, 14:55, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; yocto@yoctoproject.org
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating
Configuration Files section
On 3/5/14, 18:20, João Henrique Ferreira de Freitas joa...@gmail.com
wrote:
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 joa...@gmail.com
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
---
documentation/kernel-dev/kernel-dev-common.xml | 25
+
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the
filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment
based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the
filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file
filenamefragment.cfg/filename will be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-
WORKDIR'filenameWORKDIR/filename/ul
ink
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 filenamediffconfig/filename command creates a
file that is a
list of Linux kernel filenameCONFIG_/filename
assignments.
-It cannot be in filenamediff/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.
--
1.8.3.2
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas;
yocto@yoctoproject.org
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating
Configuration Files section
On 3/10/14, 14:55, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; yocto@yoctoproject.org
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates
Generating Configuration Files section
On 3/5/14, 18:20, João Henrique Ferreira de Freitas
joa...@gmail.com
wrote:
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 joa...@gmail.com
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
---
documentation/kernel-dev/kernel-dev-common.xml | 25
+
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the
filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment
based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the
filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file
filenamefragment.cfg/filename will be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-
WORKDIR'filenameWORKDIR/filename/ul
ink
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 filenamediffconfig/filename command creates
+ a
file that is a
list of Linux kernel filenameCONFIG_/filename
assignments.
-It cannot be in filenamediff/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.
--
1.8.3.2
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
--
Darren Hart
Yocto Project - Linux Kernel
Intel
Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
On 3/10/14, 15:02, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
Scott
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas;
yocto@yoctoproject.org
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating
Configuration Files section
On 3/10/14, 14:55, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; yocto@yoctoproject.org
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates
Generating Configuration Files section
On 3/5/14, 18:20, João Henrique Ferreira de Freitas
joa...@gmail.com
wrote:
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 joa...@gmail.com
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
---
documentation/kernel-dev/kernel-dev-common.xml | 25
+
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the
filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment
based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the
filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file
filenamefragment.cfg/filename will be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-
WORKDIR'filenameWORKDIR/filename/ul
ink
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 filenamediffconfig/filename command creates
+ a
file that is a
list of Linux kernel filenameCONFIG_/filename
assignments.
-It cannot be in filenamediff/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
Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 5:48 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas;
yocto@yoctoproject.org
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating
Configuration Files section
On 3/10/14, 15:02, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
Scott
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 5:00 PM
To: Rifenbark, Scott M; João Henrique Ferreira de Freitas;
yocto@yoctoproject.org
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates
Generating Configuration Files section
On 3/10/14, 14:55, Rifenbark, Scott M scott.m.rifenb...@intel.com
wrote:
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
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Monday, March 10, 2014 4:52 PM
To: João Henrique Ferreira de Freitas; yocto@yoctoproject.org
Cc: Rifenbark, Scott M
Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates
Generating Configuration Files section
On 3/5/14, 18:20, João Henrique Ferreira de Freitas
joa...@gmail.com
wrote:
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 joa...@gmail.com
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
---
documentation/kernel-dev/kernel-dev-common.xml | 25
+
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the
filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment
based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the
filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file
filenamefragment.cfg/filename will be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-
WORKDIR'filenameWORKDIR/filename/ul
ink
filename}/filename directory:
+literallayout class='monospaced'
+ $ bitbake linux-yocto -c diffconfig
+/literallayout/para/listitem
/orderedlist
/para
para
-Ultimately, the configuration
[yocto] [yocto-docs][PATCH] kernel-dev: Updates Generating Configuration Files section
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 joa...@gmail.com
---
documentation/kernel-dev/kernel-dev-common.xml | 25 +
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index a152f9f..de04a39 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -342,32 +342,25 @@
literallayout class='monospaced'
$ bitbake linux-yocto -c kernel_configme -f
/literallayout/para/listitem
-listitemparaCopy and rename the resulting
-filename.config/filename file (e.g.
-filenameconfig.orig/filename).
-/para/listitem
listitemparaRun the filenamemenuconfig/filename
command:
literallayout class='monospaced'
$ bitbake linux-yocto -c menuconfig
/literallayout/para/listitem
-listitemparaPrepare a configuration fragment based on
-the differences between the two files.
-/para/listitem
+listitemparaRun the filenamediffconfig/filename
+command to prepare a configuration fragment.
+The result file filenamefragment.cfg/filename will
be placed in
+filename${/filenameulink
url='YOCTO_DOCS_REF_URL;#var-WORKDIR'filenameWORKDIR/filename/ulinkfilename}/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 filenamediffconfig/filename command creates a file
that is a
list of Linux kernel filenameCONFIG_/filename assignments.
-It cannot be in filenamediff/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.
--
1.8.3.2
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
