From 50021cba20a09b1ed685db5466f940b17d4880ac Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 20 Apr 2011 14:20:19 +0100 Subject: Drop documentation directory, this is replaced by the new yocto-docs repository --- documentation/kernel-manual/Makefile | 42 - .../figures/kernel-architecture-overview.png | Bin 40748 -> 0 bytes .../kernel-manual/figures/kernel-big-picture.png | Bin 173130 -> 0 bytes .../kernel-manual/figures/kernel-title.png | Bin 14305 -> 0 bytes .../kernel-manual/figures/yocto-project-transp.png | Bin 8626 -> 0 bytes documentation/kernel-manual/kernel-concepts.xml | 335 --- documentation/kernel-manual/kernel-doc-intro.xml | 57 - documentation/kernel-manual/kernel-how-to.xml | 2178 -------------------- documentation/kernel-manual/kernel-manual.xml | 72 - documentation/kernel-manual/style.css | 968 --------- .../yocto-project-kernel-manual-customization.xsl | 8 - 11 files changed, 3660 deletions(-) delete mode 100644 documentation/kernel-manual/Makefile delete mode 100755 documentation/kernel-manual/figures/kernel-architecture-overview.png delete mode 100755 documentation/kernel-manual/figures/kernel-big-picture.png delete mode 100644 documentation/kernel-manual/figures/kernel-title.png delete mode 100755 documentation/kernel-manual/figures/yocto-project-transp.png delete mode 100644 documentation/kernel-manual/kernel-concepts.xml delete mode 100644 documentation/kernel-manual/kernel-doc-intro.xml delete mode 100644 documentation/kernel-manual/kernel-how-to.xml delete mode 100644 documentation/kernel-manual/kernel-manual.xml delete mode 100644 documentation/kernel-manual/style.css delete mode 100644 documentation/kernel-manual/yocto-project-kernel-manual-customization.xsl (limited to 'documentation/kernel-manual') diff --git a/documentation/kernel-manual/Makefile b/documentation/kernel-manual/Makefile deleted file mode 100644 index a2eaced58..000000000 --- a/documentation/kernel-manual/Makefile +++ /dev/null @@ -1,42 +0,0 @@ -XSLTOPTS = --stringparam html.stylesheet style.css \ - --stringparam chapter.autolabel 1 \ - --stringparam appendix.autolabel A \ - --stringparam section.autolabel 1 \ - --stringparam section.label.includes.component.label 1 \ - --xinclude - -## -# These URI should be rewritten by your distribution's xml catalog to -# match your localy installed XSL stylesheets. -XSL_BASE_URI = http://docbook.sourceforge.net/release/xsl/current -XSL_XHTML_URI = $(XSL_BASE_URI)/xhtml/docbook.xsl - -all: html pdf tarball - -pdf: - ../tools/poky-docbook-to-pdf kernel-manual.xml ../template - -## -# These URI should be rewritten by your distribution's xml catalog to -# match your localy installed XSL stylesheets. - -html: -# See http://www.sagehill.net/docbookxsl/HtmlOutput.html - -# xsltproc $(XSLTOPTS) -o yocto-project-qs.html $(XSL_XHTML_URI) yocto-project-qs.xml - xsltproc $(XSLTOPTS) -o kernel-manual.html yocto-project-kernel-manual-customization.xsl kernel-manual.xml - -tarball: html - tar -cvzf kernel-manual.tgz kernel-manual.html kernel-manual.pdf style.css figures/kernel-title.png figures/kernel-big-picture.png figures/kernel-architecture-overview.png - -validate: - xmllint --postvalid --xinclude --noout kernel-manual.xml - -OUTPUTS = kernel-manual.tgz kernel-manual.html kernel-manual.pdf -SOURCES = *.png *.xml *.css - -publish: - scp -r $(OUTPUTS) $(SOURCES) o-hand.com:/srv/www/pokylinux.org/doc/ - -clean: - rm -f $(OUTPUTS) diff --git a/documentation/kernel-manual/figures/kernel-architecture-overview.png b/documentation/kernel-manual/figures/kernel-architecture-overview.png deleted file mode 100755 index 2aad172db..000000000 Binary files a/documentation/kernel-manual/figures/kernel-architecture-overview.png and /dev/null differ diff --git a/documentation/kernel-manual/figures/kernel-big-picture.png b/documentation/kernel-manual/figures/kernel-big-picture.png deleted file mode 100755 index 49bac618e..000000000 Binary files a/documentation/kernel-manual/figures/kernel-big-picture.png and /dev/null differ diff --git a/documentation/kernel-manual/figures/kernel-title.png b/documentation/kernel-manual/figures/kernel-title.png deleted file mode 100644 index 965264ccc..000000000 Binary files a/documentation/kernel-manual/figures/kernel-title.png and /dev/null differ diff --git a/documentation/kernel-manual/figures/yocto-project-transp.png b/documentation/kernel-manual/figures/yocto-project-transp.png deleted file mode 100755 index 31d2b147f..000000000 Binary files a/documentation/kernel-manual/figures/yocto-project-transp.png and /dev/null differ diff --git a/documentation/kernel-manual/kernel-concepts.xml b/documentation/kernel-manual/kernel-concepts.xml deleted file mode 100644 index f26e2903e..000000000 --- a/documentation/kernel-manual/kernel-concepts.xml +++ /dev/null @@ -1,335 +0,0 @@ - - - - -Yocto Project Kernel Concepts - -
- Introduction - - This chapter provides conceptual information about the Yocto Project kernel: - - Kernel Goals - Yocto Project Kernel Development and Maintenance Overview - Kernel Architecture - Kernel Tools - - -
- -
- Kernel Goals - - The complexity of embedded kernel design has increased dramatically. - Whether it is managing multiple implementations of a particular feature or tuning and - optimizing board specific features, flexibility and maintainability are key concerns. - The Yocto Project Linux kernel is presented with the embedded - developer's needs in mind and has evolved to assist in these key concerns. - For example, prior methods such as applying hundreds of patches to an extracted - tarball have been replaced with proven techniques that allow easy inspection, - bisection and analysis of changes. - Application of these techniques also creates a platform for performing integration and - collaboration with the thousands of upstream development projects. - - - With all these considerations in mind, the Yocto Project kernel and development team - strives to attain these goals: - - Allow the end user to leverage community best practices to seamlessly - manage the development, build and debug cycles. - Create a platform for performing integration and collaboration with the - thousands of upstream development projects that exist. - Provide mechanisms that support many different work flows, front-ends and - management techniques. - Deliver the most up-to-date kernel possible while still ensuring that - the baseline kernel is the most stable official release. - Include major technological features as part of Yocto Project's up-rev - strategy. - Present a git tree, that just like the upstream kernel.org tree, has a - clear and continuous history. - Deliver a key set of supported kernel types, where each type is tailored - to a specific use case (i.g. networking, consumer, devices, and so forth). - Employ a git branching strategy that from a customer's point of view - results in a linear path from the baseline kernel.org, through a select group of features and - ends with their BSP-specific commits. - - -
- -
- Yocto Project Kernel Development and Maintenance Overview - - Yocto Project kernel, like other kernels, is based off the Linux kernel release - from . - At the beginning of our major development cycle, we choose our Yocto Project kernel - based on factors like release timing, the anticipated release timing of "final" (i.e. non "rc") - upstream kernel.org versions, and Yocto Project feature requirements. - Typically this will be a kernel that is in the - final stages of development by the community (i.e. still in the release - candidate or "rc" phase) and not yet a final release. - But by being in the final stages of external development, we know that the - kernel.org final release will clearly land within the early stages of - the Yocto Project development window. - - - This balance allows us to deliver the most up-to-date kernel - as possible, while still ensuring that we have a stable official release as - our baseline kernel version. - - - The ultimate source for the Yocto Project kernel is a released kernel - from kernel.org. - In addition to a foundational kernel from kernel.org the released - Yocto Project kernel contains a mix of important new mainline - developments, non-mainline developments (when there is no alternative), - Board Support Package (BSP) developments, - and custom features. - These additions result in a commercially released Yocto Project kernel that caters - to specific embedded designer needs for targeted hardware. - - - - Once a Yocto Project kernel is officially released the Yocto Project team goes into - their next development cycle, or "uprev" cycle while continuing maintenance on the - released kernel. - It is important to note that the most sustainable and stable way - to include feature development upstream is through a kernel uprev process. - Back-porting of hundreds of individual fixes and minor features from various - kernel versions is not sustainable and can easily compromise quality. - During the uprev cycle, the Yocto Project team uses an ongoing analysis of - kernel development, BSP support, and release timing to select the best - possible kernel.org version. - The team continually monitors community kernel - development to look for significant features of interest. - - The team does consider back-porting large features if they have a significant advantage. - User or community demand can also trigger a back-port or creation of new - functionality in the Yocto Project baseline kernel during the uprev cycle. - - - Generally speaking, every new kernel both adds features and introduces new bugs. - These consequences are the basic properties of upstream kernel development and are - managed by the Yocto Project team's kernel strategy. - It is the Yocto Project team's policy to not back-port minor features to the released kernel. - They only consider back-porting significant technological jumps - and, that is done - after a complete gap analysis. - The reason for this policy is that simply back-porting any small to medium sized change - from an evolving kernel can easily create mismatches, incompatibilities and very - subtle errors. - - - These policies result in both a stable and a cutting - edge kernel that mixes forward ports of existing features and significant and critical - new functionality. - Forward porting functionality in the Yocto Project kernel can be thought of as a - "micro uprev." - The many “micro uprevs” produce a kernel version with a mix of - important new mainline, non-mainline, BSP developments and feature integrations. - This kernel gives insight into new features and allows focused - amounts of testing to be done on the kernel, which prevents - surprises when selecting the next major uprev. - The quality of these cutting edge kernels is evolving and the kernels are used in leading edge - feature and BSP development. - -
- -
- Kernel Architecture - - This section describes the architecture of the Yocto Project kernel and provides information - on the mechanisms used to achieve that architecture. - - -
- Overview - - As mentioned earlier, a key goal of Yocto Project is to present the developer with - a kernel that has a clear and continuous history that is visible to the user. - The architecture and mechanisms used achieve that goal in a manner similar to the - upstream kernel.org. - - - - You can think of the Yocto Project kernel as consisting of a baseline kernel with - added features logically structured on top of the baseline. - The features are tagged and organized by way of a branching strategy implemented by the - source code manager (SCM) git. - The result is that the user has the ability to see the added features and - the commits that make up those features. - In addition to being able to see added features, the user can also view the history of what - made up the baseline kernel as well. - - - The following illustration shows the conceptual Yocto Project kernel. - - - - - - In the illustration, the "kernel.org Branch Point" marks the specific spot (or release) from - which the Yocto Project kernel is created. From this point "up" in the tree features and - differences are organized and tagged. - - - The "Yocto Project Baseline Kernel" contains functionality that is common to every kernel - type and BSP that is organized further up the tree. Placing these common features in the - tree this way means features don't have to be duplicated along individual branches of the - structure. - - - From the Yocto Project Baseline Kernel branch points represent specific functionality - for individual BSPs as well as real-time kernels. - The illustration represents this through three BSP-specific branches and a real-time - kernel branch. - Each branch represents some unique functionality for the BSP or a real-time kernel. - - - In this example structure, the real-time kernel branch has common features for all - real-time kernels and contains - more branches for individual BSP-specific real-time kernels. - The illustration shows three branches as an example. - Each branch points the way to specific, unique features for a respective real-time - kernel as they apply to a given BSP. - - - The resulting tree structure presents a clear path of markers (or branches) to the user - that for all practical purposes is the kernel needed for any given set of requirements. - -
- -
- Branching Strategy and Workflow - - The Yocto Project team creates kernel branches at points where functionality is - no longer shared and thus, needs to be isolated. - For example, board-specific incompatibilities would require different functionality - and would require a branch to separate the features. - Likewise, for specific kernel features the same branching strategy is used. - This branching strategy results in a tree that has features organized to be specific - for particular functionality, single kernel types, or a subset of kernel types. - This strategy results in not having to store the same feature twice internally in the - tree. - Rather we store the unique differences required to apply the feature onto the kernel type - in question. - - - The Yocto Project team strives to place features in the tree such that they can be - shared by all boards and kernel types where possible. - However, during development cycles or when large features are merged this practice - cannot always be followed. - In those cases isolated branches are used for feature merging. - - - BSP-specific code additions are handled in a similar manner to kernel-specific additions. - Some BSPs only make sense given certain kernel types. - So, for these types, we create branches off the end of that kernel type for all - of the BSPs that are supported on that kernel type. - From the perspective of the tools that create the BSP branch, the BSP is really no - different than a feature. - Consequently, the same branching strategy applies to BSPs as it does to features. - So again, rather than store the BSP twice, only the unique differences for the BSP across - the supported multiple kernels are uniquely stored. - - - While this strategy can result in a tree with a significant number of branches, it is - important to realize that from the user's point of view, there is a linear - path that travels from the baseline kernel.org, through a select group of features and - ends with their BSP-specific commits. - In other words, the divisions of the kernel are transparent and are not relevant - to the developer on a day-to-day basis. - From the user's perspective, this is the "master" branch. - They do not need not be aware of the existence of any other branches at all. - Of course there is value in the existence of these branches - in the tree, should a person decide to explore them. - For example, a comparison between two BSPs at either the commit level or at the line-by-line - code diff level is now a trivial operation. - - - Working with the kernel as a structured tree follows recognized community best practices. - In particular, the kernel as shipped with the product should be - considered an 'upstream source' and viewed as a series of - historical and documented modifications (commits). - These modifications represent the development and stabilization done - by the Yocto Project kernel development team. - - - Because commits only change at significant release points in the product life cycle, - developers can work on a branch created - from the last relevant commit in the shipped Yocto Project kernel. - As mentioned previously, the structure is transparent to the user - because the kernel tree is left in this state after cloning and building the kernel. - -
- -
- Source Code Manager - git - - The Source Code Manager (SCM) is git and it is the obvious mechanism for meeting the - previously mentioned goals. - Not only is it the SCM for kernel.org but git continues to grow in popularity and - supports many different work flows, front-ends and management techniques. - - - It should be noted that you can use as much, or as little, of what git has to offer - as is appropriate to your project. - -
-
- -
- Kernel Tools - -Since most standard workflows involve moving forward with an existing tree by -continuing to add and alter the underlying baseline, the tools that manage -Yocto Project's kernel construction are largely hidden from the developer to -present a simplified view of the kernel for ease of use. - - -The fundamental properties of the tools that manage and construct the -kernel are: - - the ability to group patches into named, reusable features - to allow top down control of included features - the binding of kernel configuration to kernel patches/features - the presentation of a seamless git repository that blends Yocto Project value with the kernel.org history and development - - - -
- - - - - - - diff --git a/documentation/kernel-manual/kernel-doc-intro.xml b/documentation/kernel-manual/kernel-doc-intro.xml deleted file mode 100644 index 05e5443b8..000000000 --- a/documentation/kernel-manual/kernel-doc-intro.xml +++ /dev/null @@ -1,57 +0,0 @@ - - - - -Yocto Project Kernel Architecture and Use Manual - -
- Introduction - - The Yocto Project presents the kernel as a fully patched, history-clean git - repository. - The git tree represents the selected features, board support, - and configurations extensively tested by Yocto Project. - The Yocto Project kernel allows the end user to leverage community - best practices to seamlessly manage the development, build and debug cycles. - - - This manual describes the Yocto Project kernel by providing information - on its history, organization, benefits, and use. - The manual consists of two sections: - - Concepts - Describes concepts behind the kernel. - You will understand how the kernel is organized and why it is organized in - the way it is. You will understand the benefits of the kernel's organization - and the mechanisms used to work with the kernel and how to apply it in your - design process. - Using the Kernel - Describes best practices and "how-to" information - that lets you put the kernel to practical use. Some examples are "How to Build a - Project Specific Tree", "How to Examine Changes in a Branch", and "Saving Kernel - Modifications." - - - - For more information on the kernel, see the following links: - - - - - - - You can find more information on Yocto Project by visiting the website at - . - - -
- - - - - - - - - diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml deleted file mode 100644 index 96325fe2a..000000000 --- a/documentation/kernel-manual/kernel-how-to.xml +++ /dev/null @@ -1,2178 +0,0 @@ - - - - -Working with the Yocto Project Kernel - - -
- Introduction - - This chapter describes how to accomplish tasks involving the kernel's tree structure. - The information covers the following: - - Tree construction - Build strategies - - Workflow examples - - - -
- -
- Tree Construction - - The Yocto Project kernel repository, as shipped with the product, is created by - compiling and executing the set of feature descriptions for every BSP/feature - in the product. - Those feature descriptions list all necessary patches, - configuration, branching, tagging and feature divisions found in the kernel. - - - You can find the files used to describe all the valid features and BSPs in the Yocto Project - kernel in any clone of the kernel git tree. - The directory meta/cfg/kernel-cache/ is a snapshot of all the kernel - configuration and feature descriptions (.scc) used to build the kernel repository. - You should realize, however, that browsing the snapshot of feature - descriptions and patches is not an effective way to determine what is in a - particular kernel branch. - Instead, you should use git directly to discover the changes - in a branch. - Using git is a efficient and flexible way to inspect changes to the kernel. - For examples showing how to use git to inspect kernel commits, see the following sections - in this chapter. - - - Ground up reconstruction of the complete kernel tree is an action only taken by the - Yocto Project team during an active development cycle. - Creating a project simply clones this tree to make it efficiently available for building - and development. - - - The general flow for constructing a project-specific kernel tree is as follows: - - A top-level kernel feature is passed to the kernel build subsystem. - Normally, this is a BSP for a particular kernel type. - - The file that describes the top-level feature is located by searching - these system directories: - - - The in-tree kernel-cache directories - - Recipe SRC_URIs - - - - For a typical build a feature description of the format: - <bsp name>-<kernel type>.scc is the target of the search. - - - Once located, the feature description is either compiled into a simple script - of actions, or an existing equivalent script that was part of the - shipped kernel is located. - - Extra features are appended to the top-level feature description. - These features can come from the KERNEL_FEATURES variable in recipes. - - Each extra feature is located, compiled and appended to the script from - step #3 - - The script is executed, and a meta-series is produced. - The meta-series is a description of all the branches, tags, patches and configuration that - needs to be applied to the base git repository to completely create the - BSP source (build) branch. - - The base repository is cloned, and the actions - listed in the meta-series are applied to the tree. - - The git repository is left with the desired branch checked out and any - required branching, patching and tagging has been performed. - - - - - The tree is now ready for configuration and compilation. - - - The end-user generated meta-series adds to the kernel as shipped with - the Yocto Project release. - Any add-ons and configuration data are applied to the end of an existing branch. - The full repository generation that is found in the - official Yocto Project kernel repositories is the combination of all - supported boards and configurations. - - This technique is flexible and allows the seamless blending of an immutable - history with additional deployment specific patches. - Any additions to the kernel become an integrated part of the branches. - - - - - -
- -
- Build Strategy - - There are some prerequisites that must be met before starting the compilation - phase of the kernel build system: - - - - There must be a kernel git repository indicated in the SRC_URI. - There must be a BSP build branch - <bsp name>-<kernel type> in 0.9 or - <kernel type>/<bsp name> in 1.0. - - - - You can typically meet these prerequisites by running the tree construction/patching phase - of the build system. - However, other means do exist. - For examples of alternate workflows such as bootstrapping a BSP, see - the Workflow Examples section in this manual. - - - - Before building a kernel it is configured by processing all of the - configuration "fragments" specified by the scc feature descriptions. - As the features are compiled, associated kernel configuration fragments are noted - and recorded in the meta-series in their compilation order. - The fragments are migrated, pre-processed and passed to the Linux Kernel - Configuration subsystem (lkc) as raw input in the form of a .config file. - The lkc uses its own internal dependency constraints to do the final - processing of that information and generates the final .config file - that is used during compilation. - - - - Using the board's architecture and other relevant values from the board's template - the Kernel compilation is started and a kernel image is produced. - - - The other thing that you will first see once you configure a kernel is that - it will generate a build tree that is separate from your git source tree. - This build tree has the name using the following form: - - linux-<BSPname>-<kerntype>-build - - "kerntype" is one of the standard kernel types. - - - - The existing support in the kernel.org tree achieves this default functionality. - - - - What this means, is that all the generated files for a particular BSP are now in this directory. - The files include the final .config, all the .o - files, the .a files, and so forth. - Since each BSP has its own separate build directory in its own separate branch - of the git tree you can easily switch between different BSP builds. - -
- - - - - -
- Workflow Examples - - - As previously noted, the Yocto Project kernel has built in git integration. - However, these utilities are not the only way to work with the kernel repository. - Yocto Project has not made changes to git or to other tools that - would invalidate alternate workflows. - Additionally, the way the kernel repository is constructed results in using - only core git functionality thus allowing any number of tools or front ends to use the - resulting tree. - - - - This section contains several workflow examples. - - -
- Change Inspection: Kernel Changes/Commits - - - A common question when working with a BSP or kernel is: - "What changes have been applied to this tree?" - - - - In projects that have a collection of directories that - contain patches to the kernel it is possible to inspect or "grep" the contents - of the directories to get a general feel for the changes. - This sort of patch inspection is not an efficient way to determine what has been done to the - kernel. - The reason it is inefficient is because there are many optional patches that are - selected based on the kernel type and the feature description. - Additionally, patches could exist in directories that are not included in the search. - - - - A more efficient way to determine what has changed in the kernel is to use - git and inspect or search the kernel tree. - This method gives you a full view of not only the source code modifications, - but also provides the reasons for the changes. - - -
- What Changed in a BSP? - - - Following are a few examples that show how to use git to examine changes. - Note that because the Yocto Project git repository does not break existing git - functionality and because there exists many permutations of these types of - commands there are many more methods to discover changes. - - - - Unless you provide a commit range - (<kernel-type>..<bsp>-<kernel-type>), kernel.org history - is blended with Yocto Project changes. - - - - # full description of the changes - > git whatchanged <kernel type>..<kernel type>/<bsp> - > eg: git whatchanged yocto/standard/base..yocto/standard/common-pc/base - - # summary of the changes - > git log --pretty=oneline --abbrev-commit <kernel type>..<kernel type>/<bsp> - - # source code changes (one combined diff) - > git diff <kernel type>..<kernel type>/<bsp> - > git show <kernel type>..<kernel type>/<bsp> - - # dump individual patches per commit - > git format-patch -o <dir> <kernel type>..<kernel type>/<bsp> - - # determine the change history of a particular file - > git whatchanged <path to file> - - # determine the commits which touch each line in a file - > git blame <path to file> - -
- -
- Show a Particular Feature or Branch Change - - - Significant features or branches are tagged in the Yocto Project tree to divide - changes. - Remember to first determine (or add) the tag of interest. - - - - Because BSP branch, kernel.org, and feature tags are all present, there are many tags. - - - - # show the changes tagged by a feature - > git show <tag> - > eg: git show yaffs2 - - # determine which branches contain a feature - > git branch --contains <tag> - - # show the changes in a kernel type - > git whatchanged yocto/base..<kernel type> - > eg: git whatchanged yocto/base..yocto/standard/base - - - - You can use many other comparisons to isolate BSP changes. - For example, you can compare against kernel.org tags (e.g. v2.6.27.18, etc), or - you can compare against subsystems (e.g. git whatchanged mm). - -
-
- -
- Development: Saving Kernel Modifications - - - Another common operation is to build a BSP supplied by Yocto Project, make some - changes, rebuild and then test. - Those local changes often need to be exported, shared or otherwise maintained. - - - - Since the Yocto Project kernel source tree is backed by git, this activity is - much easier as compared to with previous releases. - Because git tracks file modifications, additions and deletions, it is easy - to modify the code and later realize that the changes should be saved. - It is also easy to determine what has changed. - This method also provides many tools to commit, undo and export those modifications. - - - - There are many ways to save kernel modifications. - The technique employed - depends on the destination for the patches: - - - Bulk storage - Internal sharing either through patches or by using git - External submissions - Exporting for integration into another SCM - - - - - Because of the following list of issues, the destination of the patches also influences - the method for gathering them: - - - Bisectability - Commit headers - Division of subsystems for separate submission or review - - - -
- Bulk Export - - - This section describes how you can export in "bulk" changes that have not - been separated or divided. - This situation works well when you are simply storing patches outside of the kernel - source repository, either permanently or temporarily, and you are not committing - incremental changes during development. - - - - This technique is not appropriate for full integration of upstream submission - because changes are not properly divided and do not provide an avenue for per-change - commit messages. - Therefore, this example assumes that changes have not been committed incrementally - during development and that you simply must gather and export them. - - - - # bulk export of ALL modifications without separation or division - # of the changes - - > git add . - > git commit -s -a -m >commit message< - or - > git commit -s -a # and interact with $EDITOR - - - - The previous operations capture all the local changes in the project source - tree in a single git commit. - And, that commit is also stored in the project's source tree. - - - - Once the changes are exported, you can restore them manually using a template - or through integration with the default_kernel. - - -
- -
- Incremental/Planned Sharing - - - This section describes how to save modifications when you are making incremental - commits or practicing planned sharing. - The examples in this section assume that changes have been incrementally committed - to the tree during development and now need to be exported. The sections that follow - describe how you can export your changes internally through either patches or by - using git commands. - - - - During development the following commands are of interest. - For full git documentation, refer to the git man pages or to an online resource such - as . - - - # edit a file - > vi >path</file - # stage the change - > git add >path</file - # commit the change - > git commit -s - # remove a file - > git rm >path</file - # commit the change - > git commit -s - - ... etc. - - - - - Distributed development with git is possible when you use a universally - agreed-upon unique commit identifier (set by the creator of the commit) that maps to a - specific change set with a specific parent. - This identifier is created for you when - you create a commit, and is re-created when you amend, alter or re-apply - a commit. - As an individual in isolation, this is of no interest. - However, if you - intend to share your tree with normal git push and pull operations for - distributed development, you should consider the ramifications of changing a - commit that you have already shared with others. - - - - Assuming that the changes have not been pushed upstream, or pulled into - another repository, you can update both the commit content and commit messages - associated with development by using the following commands: - - - > git add >path</file - > git commit --amend - > git rebase or git rebase -i - - - - - Again, assuming that the changes have not been pushed upstream, and that - no pending works-in-progress exist (use "git status" to check) then - you can revert (undo) commits by using the following commands: - - - # remove the commit, update working tree and remove all - # traces of the change - > git reset --hard HEAD^ - # remove the commit, but leave the files changed and staged for re-commit - > git reset --soft HEAD^ - # remove the commit, leave file change, but not staged for commit - > git reset --mixed HEAD^ - - - - - You can create branches, "cherry-pick" changes or perform any number of git - operations until the commits are in good order for pushing upstream - or for pull requests. - After a push or pull, commits are normally considered - "permanent" and you should not modify them. - If they need to be changed you can incrementally do so with new commits. - These practices follow the standard "git" workflow and the kernel.org best - practices, which Yocto Project recommends. - - - - It is recommended to tag or branch before adding changes to a Yocto Project - BSP or before creating a new one. - The reason for this recommendation is because the branch or tag provides a - reference point to facilitate locating and exporting local changes. - - -
- Exporting Changes Internally by Using Patches - - - This section describes how you can extract committed changes from a working directory - by exporting them as patches. - Once extracted, you can use the patches for upstream submission, - place them in a Yocto Project template for automatic kernel patching, - or apply them in many other common uses. - - - - This example shows how to create a directory with sequentially numbered patches. - Once the directory is created, you can apply it to a repository using the - git am command to reproduce the original commit and all - the related information such as author, date, commit log, and so forth. - - - - The new commit identifiers (ID) will be generated upon re-application. - This action reflects that the commit is now applied to an underlying commit - with a different ID. - - - - - # <first-commit> can be a tag if one was created before development - # began. It can also be the parent branch if a branch was created - # before development began. - - > git format-patch -o <dir> <first commit>..<last commit> - - - - - In other words: - - # Identify commits of interest. - - # If the tree was tagged before development - > git format-patch -o <save dir> <tag> - - # If no tags are available - > git format-patch -o <save dir> HEAD^ # last commit - > git format-patch -o <save dir> HEAD^^ # last 2 commits - > git whatchanged # identify last commit - > git format-patch -o <save dir> <commit id> - > git format-patch -o <save dir> <rev-list> - - - - -
- -
- Exporting Changes Internally by Using git - - - This section describes how you can export changes from a working directory - by pushing the changes into a master repository or by making a pull request. - Once you have pushed the changes in the master repository you can then - pull those same changes into a new kernel build at a later time. - - - - Use this command form to push the changes: - - git push ssh://<master server>/<path to repo> <local branch>:<remote branch> - - - - - For example, the following command pushes the changes from your local branch - yocto/standard/common-pc/base to the remote branch with the same name - in the master repository //git.mycompany.com/pub/git/kernel-2.6.37. - - > push ssh://git.mycompany.com/pub/git/kernel-2.6.37 yocto/standard/common-pc/base:yocto/standard/common-pc/base - - - - - A pull request entails using "git request-pull" to compose an email to the - maintainer requesting that a branch be pulled into the master repository, see - for an example. - - - - Other commands such as 'git stash' or branching can also be used to save - changes, but are not covered in this document. - - - -
-
- -
- Exporting Changes for External (Upstream) Submission - - - This section describes how to export changes for external upstream submission. - If the patch series is large or the maintainer prefers to pull - changes, you can submit these changes by using a pull request. - However, it is common to sent patches as an email series. - This method allows easy review and integration of the changes. - - - - Before sending patches for review be sure you understand the - community standards for submitting and documenting changes and follow their best practices. - For example, kernel patches should follow standards such as: - - - - Documentation/SubmittingPatches (in any linux kernel source tree) - - - - - The messages used to commit changes are a large part of these standards. - Consequently, be sure that the headers for each commit have the required information. - If the initial commits were not properly documented or do not meet those standards, - you can re-base by using the "git rebase -i" command to manipulate the commits and - get them into the required format. - Other techniques such as branching and cherry-picking commits are also viable options. - - - - Once you complete the commits, you can generate the email that sends the patches - to the maintainer(s) or lists that review and integrate changes. - The command "git send-email" is commonly used to ensure that patches are properly - formatted for easy application and avoid mailer-induced patch damage. - - - - The following is an example of dumping patches for external submission: - - # dump the last 4 commits - > git format-patch --thread -n -o ~/rr/ HEAD^^^^ - > git send-email --compose --subject '[RFC 0/N] <patch series summary>' \ - --to foo@yoctoproject.org --to bar@yoctoproject.org \ - --cc list@yoctoproject.org ~/rr - # the editor is invoked for the 0/N patch, and when complete the entire - # series is sent via email for review - - -
- -
- Exporting Changes for Import into Another SCM - - - When you want to export changes for import into another - Source Code Manager (SCM) you can use any of the previously discussed - techniques. - However, if the patches are manually applied to a secondary tree and then - that tree is checked into the SCM you can lose change information such as - commit logs. - Yocto Project does not recommend this process. - - - - Many SCMs can directly import git commits, or can translate git patches so that - information is not lost. - Those facilities are SCM-dependent and you should use them whenever possible. - -
-
- -
- Working with the Yocto Project Kernel in Another SCM - - - This section describes kernel development in another SCM, which is not the same - as exporting changes to another SCM. - For this scenario you use the Yocto Project build system to - develop the kernel in a different SCM. - The following must be true for you to accomplish this: - - The delivered Yocto Project kernel must be exported into the second - SCM. - Development must be exported from that secondary SCM into a - format that can be used by the Yocto Project build system. - - - -
- Exporting the Delivered Kernel to the SCM - - - Depending on the SCM it might be possible to export the entire Yocto Project - kernel git repository, branches and all, into a new environment. - This method is preferred because it has the most flexibility and potential to maintain - the meta data associated with each commit. - - - - When a direct import mechanism is not available, it is still possible to - export a branch (or series of branches) and check them into a new repository. - - - - The following commands illustrate some of the steps you could use to - import the yocto/standard/common-pc/base kernel into a secondary SCM: - - > git checkout yocto/standard/common-pc/base - > cd .. ; echo linux/.git > .cvsignore - > cvs import -m "initial import" linux MY_COMPANY start - - - - - You could now relocate the CVS repository and use it in a centralized manner. - - - - The following commands illustrate how you can condense and merge two BSPs into a second SCM: - - > git checkout yocto/standard/common-pc/base - > git merge yocto/standard/common-pc-64/base - # resolve any conflicts and commit them - > cd .. ; echo linux/.git > .cvsignore - > cvs import -m "initial import" linux MY_COMPANY start - - -
- -
- Importing Changes for the Build - - - Once development has reached a suitable point in the second development - environment, you need to export the changes as patches. - To export them place the changes in a recipe and - automatically apply them to the kernel during patching. - - -
-
- - - - - -
- Creating a BSP Based on an Existing Similar BSP - - - This section provides an example for creating a BSP - that is based on an existing, and hopefully, similar - one. It assumes you will be using a local kernel - repository and will be pointing the kernel recipe at - that. Follow these steps and keep in mind your - particular situation and differences: - - - - Identify a machine configuration file that matches your machine. - - - - You can start with something in meta/conf/machine - - meta/conf/machine/atom-pc.conf for example. Or, you can start with a machine - configuration from any of the BSP layers in the meta-intel repository at - , such as - meta-intel/meta-emenlow/conf/machine/emenlow.conf. - - - - The main difference between the two is that "emenlow" is in its own layer. - It is in its own layer because it needs extra machine-specific packages such as its - own video driver and other supporting packages. - The "atom-pc" is simpler and does not need any special packages - everything it needs can - be specified in the configuration file. - The "atom-pc" machine also supports all of Asus eee901, Acer Aspire One, Toshiba NB305, - and the Intel® Embedded Development Board 1-N450 with no changes. - - - - If you want to make minor changes to support a slightly different machine, you can - create a new configuration file for it and add it alongside the others. - You might consider keeping the common information separate and including it. - - - - Similarly, you can also use multiple configuration files for different machines even - if you do it as a separate layer like meta-emenlow. - - - - As an example consider this: - - Copy meta-emenlow to meta-mymachine - Fix or remove anything you do not need. - For this example the only thing left was the kernel directory with a - linux-yocto_git.bbappend - file - and meta-mymachine/conf/machine/mymachine.conf - (linux-yocto is the kernel listed in - meta-emenlow/conf/machine/emenlow.conf). - Add a new entry in the build/conf/bblayers.conf - so the new layer can be found by BitBake. - - - - - Create a machine branch for your machine. - - - - For the kernel to compile successfully, you need to create a branch in the git repository - specifically named for your machine. - To create this branch first create a bare clone of the Yocto Project git repository. - Next, create a local clone of that: - - $ git clone --bare git://git.yoctoproject.org/linux-yocto-2.6.37.git - linux-yocto-2.6.37.git - $ git clone linux-yocto-2.6.37.git linux-yocto-2.6.37 - - - - - Now create a branch in the local clone and push it to the bare clone: - - $ git checkout -b yocto/standard/mymachine origin/yocto/standard/base - $ git push origin yocto/standard/mymachine:yocto/standard/mymachine - - - - - In a layer, create a linux-yocto_git.bbappend - file with the following: - - - - - FILESEXTRAPATHS := "${THISDIR}/${PN}" - COMPATIBLE_MACHINE_mymachine = "mymachine" - - # It is often nice to have a local clone of the kernel repository, to - # allow patches to be staged, branches created, and so forth. Modify - # KSRC to point to your local clone as appropriate. - - KSRC ?= /path/to/your/bare/clone/for/example/linux-yocto-2.6.37.git - - # KMACHINE is the branch to be built, or alternatively - # KBRANCH can be directly set. - # KBRANCH is set to KMACHINE in the main linux-yocto_git.bb - # KBRANCH ?= "${LINUX_KERNEL_TYPE}/${KMACHINE}" - - KMACHINE_mymachine = "yocto/standard/mymachine" - - SRC_URI = "git://${KSRC};nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" - - - - - After doing that, select the machine in build/conf/local.conf: - - # - MACHINE ?= "mymachine" - # - - - - - You should now be able to build and boot an image with the new kernel: - - $ bitbake poky-image-sato-live - - - - - Modify the kernel configuration for your machine. - - - - Of course, that will give you a kernel with the default configuration file, which is probably - not what you want. - If you just want to set some kernel configuration options, you can do that by - putting them in a file. - For example, inserting the following into some .cfg file: - - CONFIG_NETDEV_1000=y - CONFIG_E1000E=y - - - - - And, another .cfg file would contain: - - CONFIG_LOG_BUF_SHIFT=18 - - - - These config fragments could then be picked up and - applied to the kernel .config by appending them to the kernel SRC_URI: - - - - SRC_URI_append_mymachine = " file://some.cfg \ - file://other.cfg \ - " - - - - - You could also add these directly to the git repository meta - branch as well. - However, the former method is a simple starting point. - - - - If you're also adding patches to the kernel, you can do the same thing. - Put your patches in the SRC_URI as well (plus .cfg for their kernel - configuration options if needed). - - - - Practically speaking, to generate the patches, you'd go to the source in the build tree: - - build/tmp/work/mymachine-poky-linux/linux-yocto-2.6.37+git0+d1cd5c80ee97e81e130be8c3de3965b770f320d6_0+ -0431115c9d720fee5bb105f6a7411efb4f851d26-r13/linux - - - - - Then, modify the code there, using quilt to save the changes, and recompile until - it works: - - $ bitbake -c compile -f linux-yocto - - - - - Once you have the final patch from quilt, copy it to the - SRC_URI location. - The patch is applied the next time you do a clean build. - Of course, since you have a branch for the BSP in git, it would be better to put it there instead. - For example, in this case, commit the patch to the "yocto/standard/mymachine" branch, and during the - next build it is applied from there. - - - -
- -
- Creating a BSP Based on an Existing Similar BSP Without a Local Kernel Repository - - - If you are creating a BSP based on an existing similar BSP but you do not have - a local kernel repository, the process is very similar to the process in - the previous section (). - - - - Follow the exact same process as described in the previous section with - these slight modifications: - - - Perform Step 1 as is from the previous section. - Perform Step 2 as is from the previous section. - Perform Step 3 but do not modify the - KSRC line in the bbappend file. - Edit the local.conf so - that it contains the following: - - YOCTO_KERNEL_EXTERNAL_BRANCH="<your-machine>-standard - - Adding this statement to the file triggers BSP bootstrapping - to occur and the correct branches and base configuration to be used. - - Perform Step 4 as is from the previous section. - Perform Step 5 as is from the previous section. - -
- - - - - - - - - - -
- "-dirty" String - - - If kernel images are being built with "-dirty" on the end of the version - string, this simply means that modifications in the source - directory have not been committed. - - > git status - - - - - You can use the git command above to report modified, removed, or added files. - You should commit those changes to the tree regardless of whether they will be saved, - exported, or used. - Once you commit the changes you need to rebuild the kernel. - - - - To brute force pickup and commit all such pending changes enter the following: - - > git add . - > git commit -s -a -m "getting rid of -dirty" - - - - - Next, rebuild the kernel. - -
- - - - - - - - - - - - -
- - - - - - - - - - diff --git a/documentation/kernel-manual/kernel-manual.xml b/documentation/kernel-manual/kernel-manual.xml deleted file mode 100644 index 875cbe314..000000000 --- a/documentation/kernel-manual/kernel-manual.xml +++ /dev/null @@ -1,72 +0,0 @@ - - - - - - - - - - - - - - - - Bruce Ashfield - - Wind River Corporation - - bruce.ashfield@windriver.com - - - - - - 0.9 - 24 November 2010 - This revision is the initial document draft and corresponds with - the Yocto Project 0.9 Release. - - - 1.0 - 6 April 2011 - This revision corresponds with the Yocto Project 1.0 Release. - - - - - 2010-2011 - Linux Foundation - - - - - Permission is granted to copy, distribute and/or modify this document under - the terms of the Creative Commons Attribution-Share Alike 2.0 UK: England & Wales as published by Creative Commons. - - - - - - - - - - - - - - - diff --git a/documentation/kernel-manual/style.css b/documentation/kernel-manual/style.css deleted file mode 100644 index 33a01d125..000000000 --- a/documentation/kernel-manual/style.css +++ /dev/null @@ -1,968 +0,0 @@ -/* - Generic XHTML / DocBook XHTML CSS Stylesheet. - - Browser wrangling and typographic design by - Oyvind Kolas / pippin@gimp.org - - Customised for Poky by - Matthew Allum / mallum@o-hand.com - - Thanks to: - Liam R. E. Quin - William Skaggs - Jakub Steiner - - Structure - --------- - - The stylesheet is divided into the following sections: - - Positioning - Margins, paddings, width, font-size, clearing. - Decorations - Borders, style - Colors - Colors - Graphics - Graphical backgrounds - Nasty IE tweaks - Workarounds needed to make it work in internet explorer, - currently makes the stylesheet non validating, but up until - this point it is validating. - Mozilla extensions - Transparency for footer - Rounded corners on boxes - -*/ - - - /*************** / - / Positioning / -/ ***************/ - -body { - font-family: Verdana, Sans, sans-serif; - - min-width: 640px; - width: 80%; - margin: 0em auto; - padding: 2em 5em 5em 5em; - color: #333; -} - -.reviewer { - color: red; -} - -h1,h2,h3,h4,h5,h6,h7 { - font-family: Arial, Sans; - color: #00557D; - clear: both; -} - -h1 { - font-size: 2em; - text-align: left; - padding: 0em 0em 0em 0em; - margin: 2em 0em 0em 0em; -} - -h2.subtitle { - margin: 0.10em 0em 3.0em 0em; - padding: 0em 0em 0em 0em; - font-size: 1.8em; - padding-left: 20%; - font-weight: normal; - font-style: italic; -} - -h2 { - margin: 2em 0em 0.66em 0em; - padding: 0.5em 0em 0em 0em; - font-size: 1.5em; - font-weight: bold; -} - -h3.subtitle { - margin: 0em 0em 1em 0em; - padding: 0em 0em 0em 0em; - font-size: 142.14%; - text-align: right; -} - -h3 { - margin: 1em 0em 0.5em 0em; - padding: 1em 0em 0em 0em; - font-size: 140%; - font-weight: bold; -} - -h4 { - margin: 1em 0em 0.5em 0em; - padding: 1em 0em 0em 0em; - font-size: 120%; - font-weight: bold; -} - -h5 { - margin: 1em 0em 0.5em 0em; - padding: 1em 0em 0em 0em; - font-size: 110%; - font-weight: bold; -} - -h6 { - margin: 1em 0em 0em 0em; - padding: 1em 0em 0em 0em; - font-size: 80%; - font-weight: bold; -} - -.authorgroup { - background-color: transparent; - background-repeat: no-repeat; - padding-top: 256px; - background-image: url("figures/kernel-title.png"); - background-position: left top; - margin-top: -256px; - padding-right: 50px; - margin-left: 0px; - text-align: right; - width: 740px; -} - -h3.author { - margin: 0em 0me 0em 0em; - padding: 0em 0em 0em 0em; - font-weight: normal; - font-size: 100%; - color: #333; - clear: both; -} - -.author tt.email { - font-size: 66%; -} - -.titlepage hr { - width: 0em; - clear: both; -} - -.revhistory { - padding-top: 2em; - clear: both; -} - -.toc, -.list-of-tables, -.list-of-examples, -.list-of-figures { - padding: 1.33em 0em 2.5em 0em; - color: #00557D; -} - -.toc p, -.list-of-tables p, -.list-of-figures p, -.list-of-examples p { - padding: 0em 0em 0em 0em; - padding: 0em 0em 0.3em; - margin: 1.5em 0em 0em 0em; -} - -.toc p b, -.list-of-tables p b, -.list-of-figures p b, -.list-of-examples p b{ - font-size: 100.0%; - font-weight: bold; -} - -.toc dl, -.list-of-tables dl, -.list-of-figures dl, -.list-of-examples dl { - margin: 0em 0em 0.5em 0em; - padding: 0em 0em 0em 0em; -} - -.toc dt { - margin: 0em 0em 0em 0em; - padding: 0em 0em 0em 0em; -} - -.toc dd { - margin: 0em 0em 0em 2.6em; - padding: 0em 0em 0em 0em; -} - -div.glossary dl, -div.variablelist dl { -} - -.glossary dl dt, -.variablelist dl dt, -.variablelist dl dt span.term { - font-weight: normal; - width: 20em; - text-align: right; -} - -.variablelist dl dt { - margin-top: 0.5em; -} - -.glossary dl dd, -.variablelist dl dd { - margin-top: -1em; - margin-left: 25.5em; -} - -.glossary dd p, -.variablelist dd p { - margin-top: 0em; - margin-bottom: 1em; -} - - -div.calloutlist table td { - padding: 0em 0em 0em 0em; - margin: 0em 0em 0em 0em; -} - -div.calloutlist table td p { - margin-top: 0em; - margin-bottom: 1em; -} - -div p.copyright { - text-align: left; -} - -div.legalnotice p.legalnotice-title { - margin-bottom: 0em; -} - -p { - line-height: 1.5em; - margin-top: 0em; - -} - -dl { - padding-top: 0em; -} - -hr { - border: solid 1px; -} - - -.mediaobject, -.mediaobjectco { - text-align: center; -} - -img { - border: none; -} - -ul { - padding: 0em 0em 0em 1.5em; -} - -ul li { - padding: 0em 0em 0em 0em; -} - -ul li p { - text-align: left; -} - -table { - width :100%; -} - -th { - padding: 0.25em; - text-align: left; - font-weight: normal; - vertical-align: top; -} - -td { - padding: 0.25em; - vertical-align: top; -} - -p a[id] { - margin: 0px; - padding: 0px; - display: inline; - background-image: none; -} - -a { - text-decoration: underline; - color: #444; -} - -pre { - overflow: auto; -} - -a:hover { - text-decoration: underline; - /*font-weight: bold;*/ -} - - -div.informalfigure, -div.informalexample, -div.informaltable, -div.figure, -div.table, -div.example { - margin: 1em 0em; - padding: 1em; - page-break-inside: avoid; -} - - -div.informalfigure p.title b, -div.informalexample p.title b, -div.informaltable p.title b, -div.figure p.title b, -div.example p.title b, -div.table p.title b{ - padding-top: 0em; - margin-top: 0em; - font-size: 100%; - font-weight: normal; -} - -.mediaobject .caption, -.mediaobject .caption p { - text-align: center; - font-size: 80%; - padding-top: 0.5em; - padding-bottom: 0.5em; -} - -.epigraph { - padding-left: 55%; - margin-bottom: 1em; -} - -.epigraph p { - text-align: left; -} - -.epigraph .quote { - font-style: italic; -} -.epigraph .attribution { - font-style: normal; - text-align: right; -} - -span.application { - font-style: italic; -} - -.programlisting { - font-family: monospace; - font-size: 80%; - white-space: pre; - margin: 1.33em 0em; - padding: 1.33em; -} - -.tip, -.warning, -.caution, -.note { - margin-top: 1em; - margin-bottom: 1em; - -} - -/* force full width of table within div */ -.tip table, -.warning table, -.caution table, -.note table { - border: none; - width: 100%; -} - - -.tip table th, -.warning table th, -.caution table th, -.note table th { - padding: 0.8em 0.0em 0.0em 0.0em; - margin : 0em 0em 0em 0em; -} - -.tip p, -.warning p, -.caution p, -.note p { - margin-top: 0.5em; - margin-bottom: 0.5em; - padding-right: 1em; - text-align: left; -} - -.acronym { - text-transform: uppercase; -} - -b.keycap, -.keycap { - padding: 0.09em 0.3em; - margin: 0em; -} - -.itemizedlist li { - clear: none; -} - -.filename { - font-size: medium; - font-family: Courier, monospace; -} - - -div.navheader, div.heading{ - position: absolute; - left: 0em; - top: 0em; - width: 100%; - background-color: #cdf; - width: 100%; -} - -div.navfooter, div.footing{ - position: fixed; - left: 0em; - bottom: 0em; - background-color: #eee; - width: 100%; -} - - -div.navheader td, -div.navfooter td { - font-size: 66%; -} - -div.navheader table th { - /*font-family: Georgia, Times, serif;*/ - /*font-size: x-large;*/ - font-size: 80%; -} - -div.navheader table { - border-left: 0em; - border-right: 0em; - border-top: 0em; - width: 100%; -} - -div.navfooter table { - border-left: 0em; - border-right: 0em; - border-bottom: 0em; - width: 100%; -} - -div.navheader table td a, -div.navfooter table td a { - color: #777; - text-decoration: none; -} - -/* normal text in the footer */ -div.navfooter table td { - color: black; -} - -div.navheader table td a:visited, -div.navfooter table td a:visited { - color: #444; -} - - -/* links in header and footer */ -div.navheader table td a:hover, -div.navfooter table td a:hover { - text-decoration: underline; - background-color: transparent; - color: #33a; -} - -div.navheader hr, -div.navfooter hr { - display: none; -} - - -.qandaset tr.question td p { - margin: 0em 0em 1em 0em; - padding: 0em 0em 0em 0em; -} - -.qandaset tr.answer td p { - margin: 0em 0em 1em 0em; - padding: 0em 0em 0em 0em; -} -.answer td { - padding-bottom: 1.5em; -} - -.emphasis { - font-weight: bold; -} - - - /************* / - / decorations / -/ *************/ - -.titlepage { -} - -.part .title { -} - -.subtitle { - border: none; -} - -/* -h1 { - border: none; -} - -h2 { - border-top: solid 0.2em; - border-bottom: solid 0.06em; -} - -h3 { - border-top: 0em; - border-bottom: solid 0.06em; -} - -h4 { - border: 0em; - border-bottom: solid 0.06em; -} - -h5 { - border: 0em; -} -*/ - -.programlisting { - border: solid 1px; -} - -div.figure, -div.table, -div.informalfigure, -div.informaltable, -div.informalexample, -div.example { - border: 1px solid; -} - - - -.tip, -.warning, -.caution, -.note { - border: 1px solid; -} - -.tip table th, -.warning table th, -.caution table th, -.note table th { - border-bottom: 1px solid; -} - -.question td { - border-top: 1px solid black; -} - -.answer { -} - - -b.keycap, -.keycap { - border: 1px solid; -} - - -div.navheader, div.heading{ - border-bottom: 1px solid; -} - - -div.navfooter, div.footing{ - border-top: 1px solid; -} - - /********* / - / colors / -/ *********/ - -body { - color: #333; - background: white; -} - -a { - background: transparent; -} - -a:hover { - background-color: #dedede; -} - - -h1, -h2, -h3, -h4, -h5, -h6, -h7, -h8 { - background-color: transparent; -} - -hr { - border-color: #aaa; -} - - -.tip, .warning, .caution, .note { - border-color: #aaa; -} - - -.tip table th, -.warning table th, -.caution table th, -.note table th { - border-bottom-color: #aaa; -} - - -.warning { - background-color: #fea; -} - -.caution { - background-color: #fea; -} - -.tip { - background-color: #eff; -} - -.note { - background-color: #dfc; -} - -.glossary dl dt, -.variablelist dl dt, -.variablelist dl dt span.term { - color: #044; -} - -div.figure, -div.table, -div.example, -div.informalfigure, -div.informaltable, -div.informalexample { - border-color: #aaa; -} - -pre.programlisting { - color: black; - background-color: #fff; - border-color: #aaa; - border-width: 2px; -} - -.guimenu, -.guilabel, -.guimenuitem { - background-color: #eee; -} - - -b.keycap, -.keycap { - background-color: #eee; - border-color: #999; -} - - -div.navheader { - border-color: black; -} - - -div.navfooter { - border-color: black; -} - - - /*********** / - / graphics / -/ ***********/ - -/* -body { - background-image: url("images/body_bg.jpg"); - background-attachment: fixed; -} - -.navheader, -.note, -.tip { - background-image: url("images/note_bg.jpg"); - background-attachment: fixed; -} - -.warning, -.caution { - background-image: url("images/warning_bg.jpg"); - background-attachment: fixed; -} - -.figure, -.informalfigure, -.example, -.informalexample, -.table, -.informaltable { - background-image: url("images/figure_bg.jpg"); - background-attachment: fixed; -} - -*/ -h1, -h2, -h3, -h4, -h5, -h6, -h7{ -} - -/* -Example of how to stick an image as part of the title. - -div.article .titlepage .title -{ - background-image: url("figures/white-on-black.png"); - background-position: center; - background-repeat: repeat-x; -} -*/ - -div.preface .titlepage .title, -div.colophon .title, -div.chapter .titlepage .title, -div.article .titlepage .title -{ -} - -div.section div.section .titlepage .title, -div.sect2 .titlepage .title { - background: none; -} - - -h1.title { - background-color: transparent; - background-image: url("figures/yocto-project-bw.png"); - background-repeat: no-repeat; - height: 256px; - text-indent: -9000px; - overflow:hidden; -} - -h2.subtitle { - background-color: transparent; - text-indent: -9000px; - overflow:hidden; - width: 0px; - display: none; -} - - /*************************************** / - / pippin.gimp.org specific alterations / -/ ***************************************/ - -/* -div.heading, div.navheader { - color: #777; - font-size: 80%; - padding: 0; - margin: 0; - text-align: left; - position: absolute; - top: 0px; - left: 0px; - width: 100%; - height: 50px; - background: url('/gfx/heading_bg.png') transparent; - background-repeat: repeat-x; - background-attachment: fixed; - border: none; -} - -div.heading a { - color: #444; -} - -div.footing, div.navfooter { - border: none; - color: #ddd; - font-size: 80%; - text-align:right; - - width: 100%; - padding-top: 10px; - position: absolute; - bottom: 0px; - left: 0px; - - background: url('/gfx/footing_bg.png') transparent; -} -*/ - - - - /****************** / - / nasty ie tweaks / -/ ******************/ - -/* -div.heading, div.navheader { - width:expression(document.body.clientWidth + "px"); -} - -div.footing, div.navfooter { - width:expression(document.body.clientWidth + "px"); - margin-left:expression("-5em"); -} -body { - padding:expression("4em 5em 0em 5em"); -} -*/ - - /**************************************** / - / mozilla vendor specific css extensions / -/ ****************************************/ -/* -div.navfooter, div.footing{ - -moz-opacity: 0.8em; -} - -div.figure, -div.table, -div.informalfigure, -div.informaltable, -div.informalexample, -div.example, -.tip, -.warning, -.caution, -.note { - -moz-border-radius: 0.5em; -} - -b.keycap, -.keycap { - -moz-border-radius: 0.3em; -} -*/ - -table tr td table tr td { - display: none; -} - - -hr { - display: none; -} - -table { - border: 0em; -} - - .photo { - float: right; - margin-left: 1.5em; - margin-bottom: 1.5em; - margin-top: 0em; - max-width: 17em; - border: 1px solid gray; - padding: 3px; - background: white; -} - .seperator { - padding-top: 2em; - clear: both; - } - - #validators { - margin-top: 5em; - text-align: right; - color: #777; - } - @media print { - body { - font-size: 8pt; - } - .noprint { - display: none; - } - } - - -.tip, -.note { - background: #666666; - color: #fff; - padding: 20px; - margin: 20px; -} - -.tip h3, -.note h3 { - padding: 0em; - margin: 0em; - font-size: 2em; - font-weight: bold; - color: #fff; -} - -.tip a, -.note a { - color: #fff; - text-decoration: underline; -} diff --git a/documentation/kernel-manual/yocto-project-kernel-manual-customization.xsl b/documentation/kernel-manual/yocto-project-kernel-manual-customization.xsl deleted file mode 100644 index 8eb69050b..000000000 --- a/documentation/kernel-manual/yocto-project-kernel-manual-customization.xsl +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - -- cgit v1.2.3