| Summary: | linux-yocto based recipes require a config (won't use Linux defconfig) | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Darren Hart <dvhart> |
| Component: | kernel-tooling | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, srifenbark, yp.kernel.watcher, yp.watcher |
| Version: | 1.7 | ||
| Target Milestone: | 1.9 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 17 June 2015: Documentation revisions made. Needs review. | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Darren Hart
2014-08-05 19:55:41 UTC
It's a documentation issue, since you must specify something for a configuration .. i.e. a defconfig or fragments. That being said, the error message for this is really nasty, so I can take the bug and use it to improve the message, which is the documentation. We'll need to update the kernel-dev manual as well. Adding Scott. I've emailed Scott on this. Looking for the right place to document it. Hi, I have a section in the YP Linux Kernel Development Manual that is titled "Modifying an Existing Recipe" (http://www.yoctoproject.org/docs/kernel-dev/kernel-dev.html#modifying-an-existing-recipe). This section has some sub-sections. Originally, I thought that we could address this with a note in the section that talks about changing the configuration. Bruce indicates, though, that it is not quite the same. So, if this involves only "using" custom Linux-yocto kernels and does not involve creating them, which is what I thought this existing section would cover, then do we want a brand new section called "Using Custom Linux-Yocto Kernel Recipes"? Scott Hi, I found what I think would be an appropriate section to note this requirement when using the yocto-linux-custom.bb recipe. I have added a step to the list and noted some more information in the description of SRC_URI. Please look this over and let me know if this will meet the documentation requirement of this bug. http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-your-own-sources See step 3 and the description for SRC_URI in step 4. Thanks, Scott (In reply to comment #5) > Hi, > > I found what I think would be an appropriate section to note this > requirement when using the yocto-linux-custom.bb recipe. I have added a > step to the list and noted some more information in the description of > SRC_URI. Please look this over and let me know if this will meet the > documentation requirement of this bug. > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > your-own-sources > > See step 3 and the description for SRC_URI in step 4. > > Thanks, > Scott (In reply to comment #5) > Hi, > > I found what I think would be an appropriate section to note this > requirement when using the yocto-linux-custom.bb recipe. I have added a > step to the list and noted some more information in the description of > SRC_URI. Please look this over and let me know if this will meet the > documentation requirement of this bug. > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > your-own-sources > > See step 3 and the description for SRC_URI in step 4. We should add more text around step #3. When you do a 'make defconfig', you are getting the kernel defined default configuration for your architecture, but there is no guarantee that it is valid for your use case, or will even boot your board. This is particularly true in non-x86 architectures. To use non-x86 defconfigs, you need to be a bit more specific and fine one that matches your board. i.e. for arm, you look in "arch/arm/configs" and fine the one that is the best starting point for your board. Alternatively, your board vendor may supply a baseline .config, that you copy into place and call 'defconfig'. The SRC_URI changes look fine. > > Thanks, > Scott (In reply to comment #6) > (In reply to comment #5) > > Hi, > > > > I found what I think would be an appropriate section to note this > > requirement when using the yocto-linux-custom.bb recipe. I have added a > > step to the list and noted some more information in the description of > > SRC_URI. Please look this over and let me know if this will meet the > > documentation requirement of this bug. > > > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > > your-own-sources > > > > See step 3 and the description for SRC_URI in step 4. > > > > Thanks, > > Scott > > (In reply to comment #5) > > Hi, > > > > I found what I think would be an appropriate section to note this > > requirement when using the yocto-linux-custom.bb recipe. I have added a > > step to the list and noted some more information in the description of > > SRC_URI. Please look this over and let me know if this will meet the > > documentation requirement of this bug. > > > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > > your-own-sources > > > > See step 3 and the description for SRC_URI in step 4. > > We should add more text around step #3. When you do a 'make defconfig', > you are getting the kernel defined default configuration for your > architecture, but there is no guarantee that it is valid for your > use case, or will even boot your board. This is particularly true in > non-x86 architectures. To use non-x86 defconfigs, you need to be a > bit more specific and fine one that matches your board. > > i.e. for arm, you look in "arch/arm/configs" and fine the one that > is the best starting point for your board. > > Alternatively, your board vendor may supply a baseline .config, that > you copy into place and call 'defconfig'. Bruce, Check out http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-your-own-sources section and Step 3 now. I have your suggestions in. Let me know if this works. > > The SRC_URI changes look fine. > > > > > > Thanks, > > Scott (In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Hi, > > > > > > I found what I think would be an appropriate section to note this > > > requirement when using the yocto-linux-custom.bb recipe. I have added a > > > step to the list and noted some more information in the description of > > > SRC_URI. Please look this over and let me know if this will meet the > > > documentation requirement of this bug. > > > > > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > > > your-own-sources > > > > > > See step 3 and the description for SRC_URI in step 4. > > > > > > Thanks, > > > Scott > > > > (In reply to comment #5) > > > Hi, > > > > > > I found what I think would be an appropriate section to note this > > > requirement when using the yocto-linux-custom.bb recipe. I have added a > > > step to the list and noted some more information in the description of > > > SRC_URI. Please look this over and let me know if this will meet the > > > documentation requirement of this bug. > > > > > > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > > > your-own-sources > > > > > > See step 3 and the description for SRC_URI in step 4. > > > > We should add more text around step #3. When you do a 'make defconfig', > > you are getting the kernel defined default configuration for your > > architecture, but there is no guarantee that it is valid for your > > use case, or will even boot your board. This is particularly true in > > non-x86 architectures. To use non-x86 defconfigs, you need to be a > > bit more specific and fine one that matches your board. > > > > i.e. for arm, you look in "arch/arm/configs" and fine the one that > > is the best starting point for your board. > > > > Alternatively, your board vendor may supply a baseline .config, that > > you copy into place and call 'defconfig'. > > Bruce, Check out > http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with- > your-own-sources section and Step 3 now. I have your suggestions in. Let > me know if this works. This looks good to me. Bruce > > > > > The SRC_URI changes look fine. > > > > > > > > > > Thanks, > > > Scott |