diff options
-rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 06aa99b7bf..1c89550c01 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
@@ -561,6 +561,52 @@ | |||
561 | <section id="platdev-newmachine"> | 561 | <section id="platdev-newmachine"> |
562 | <title>Porting the Yocto Project to a New Machine</title> | 562 | <title>Porting the Yocto Project to a New Machine</title> |
563 | 563 | ||
564 | <!-- | ||
565 | WRITER NOTES: | ||
566 | |||
567 | I had this chat with Richard: | ||
568 | |||
569 | scottrif: Terminology question: We speak of "New Machines" or "Adding a New Machine" | ||
570 | in YP. Are "Machines" restricted to architectures? In poky/meta/conf/machine we have .conf | ||
571 | files for the five architectures. What exactly does the term "Machine" mean? | ||
572 | |||
573 | RP: no, each architecture has multiple different machines. A "machine" can correspond | ||
574 | to a particular reference board or hardware product | ||
575 | we just have one reference machine per architecture | ||
576 | We're a little vague sometimes as "machine" can refer to either an individual platform, | ||
577 | or in some cases a set of different platforms with common structure | ||
578 | (e.g. netbooks) | ||
579 | |||
580 | scottrif: So our reference machines we supply are the five qemu* machines? | ||
581 | |||
582 | RP: in oe-core, plus one "real" target in meta-yocto | ||
583 | (per arch) | ||
584 | |||
585 | scottrif: I see four in meta-yocto/conf/machine. Shouldn't there be five if there is one | ||
586 | "real" target per architecture? | ||
587 | |||
588 | RP: yes, we don't have one for x86_64 :/ | ||
589 | |||
590 | scottrif: I think it is a bit difficult to map our four poky/meta-yocto/conf/machines to one of our | ||
591 | five architectures. Some have key words in there that identify the architecture but | ||
592 | beagleboard and atom-pc don't. | ||
593 | We have a section that describes adding a Machine Configuration file to Yocto and | ||
594 | it states that TARGET_ARCH is one of the most important variables that need to be | ||
595 | set in the .conf file. The four I am looking at don't have that variable. | ||
596 | |||
597 | RP: That has changed a little now. You need to include the appropriate tune file | ||
598 | which will set it for you | ||
599 | People had a tendency not to set all the right pieces so it got abstracted | ||
600 | |||
601 | scottrif: Got it. I see them in poky/meta/conf/machine/include. | ||
602 | |||
603 | SOME CONCLUSIONS: | ||
604 | |||
605 | I need to define the term machine. It is confusing. Then, this section needs to be cleared up | ||
606 | so that there are some definite steps on how to do this. I need more detail here. | ||
607 | |||
608 | --> | ||
609 | |||
564 | <para> | 610 | <para> |
565 | Adding a new machine to the Yocto Project is a straightforward process. | 611 | Adding a new machine to the Yocto Project is a straightforward process. |
566 | This section provides information that gives you an idea of the changes you must make. | 612 | This section provides information that gives you an idea of the changes you must make. |