| Summary: | add pointer to kernel architecture manuals | ||
|---|---|---|---|
| Product: | [Documentation] Kernel Development | Reporter: | Peter A. Bigot <pab> |
| Component: | kernel-development | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | bruce.ashfield, dvhart, srifenbark |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 07 October 2013: RESOLVED | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Done (doc changes complete) | |
|
Description
Peter A. Bigot
2013-09-01 12:22:35 UTC
Currently, we have a "Yocto Project Linux Kernel Development Manual" listed on our Yocto Project website (http://www.yoctoproject.org). This manual is a mainstream YP manual that is visible at the same level as the other YP manuals from the "Documentation" page of the website. I don't understand the exact nature of this bug where you say links should be made in the "Other Resources" section. Can you explain in more detail where you think the links should be? Thanks, Scott Sorry; I thought that was implicit since this bugzilla product showed up as: Kernel Development: Defects within the Yocto Project's Kernel Development Manual. Recent discussion as referenced revealed that there is additional detail that was removed from earlier versions of that manual. This detail would help new kernel developers understand how the underlying system works. So yes, once Bruce (not "Brusce", sorry about that) locates the new location of the relevant material a link to it should be added to the "Other Resources" section of the "Yocto Project Linux Kernel Development Manual". Ahh... got it now. Ok - I will update that section of the manual when we get some information from Bruce. I should have understood that the section was in the manual that the bug was filed against :) My bad. Thanks, Scott I agree the kernel dev manual should link to the architecture manual, but we need to cautious regarding what we put in the architecture manual. If the information is needed to make use of the linux-yocto tooling for BSPs or recipes, it belongs in the development manual. Scott, do you have the necessary information to move to Accepted? If not, what is missing? I don't have the location of the information that was in the old architecture manual so I can't point to it. BTW - the old architecture manual was retired last release so we can't reference it. I am unsure at this point if any information we culled from the old architecture manual surfaced in a different form that we could reference. Scott I thought the relevant bits had been moved to the appendix of the kernel-dev manual? Appendix A covers the old branching strategy and organization stuff and Appendix B covers kernel maintence, which was also from the old architecture manual. Here are some links. Does this satisfy the bug? http://www.yoctoproject.org/docs/1.5/kernel-dev/kernel-dev.html#kernel-dev-concepts-appx http://www.yoctoproject.org/docs/1.5/kernel-dev/kernel-dev.html#kernel-dev-maint-appx Scott If there isn't anything else available, then there's certainly no way to add a link to it. I'll leave the final assessment to Bruce since he knows what information he thought had been moved somewhere else. The appendixes were there before I had trouble figuring out how to manage kernel metadata, and I did read them, so there's still documentation to be added but that's not part of this 1.5-oriented bug. Let me see what I can dig up for this. I've been squashing other bugs, but am back to documentation updates now. I had a look, and yes, the appendixes are part of the information I was thinking of. I also have a "linux-yocto from scratch" document that I wrote, which likely fills in the missing gaps. So for 1.5, perhaps we can consider this "done" (if you can call it that), and for 1.6, I can queue up the new content, working with Peter to make sure it covers the areas he is looking for. That'd work for me. Thanks. Hi, Okay, so based on the last few comments, I am going to mark this bug RESOLVED and the doc changes as "completed." Thanks, Scott |