diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2018-01-29 15:18:03 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-02-14 15:25:29 +0000 |
commit | ae06e04cd225d2c2147ca355e2dd39b4f6cf6775 (patch) | |
tree | c920e85262a91e7626279e7dcbbd56a299919f49 /documentation/getting-started/eclipse/html/getting-started/x32.html | |
parent | ebc7de094881dd8f2450aa4fdf548f2e9c835df1 (diff) | |
download | poky-ae06e04cd225d2c2147ca355e2dd39b4f6cf6775.tar.gz |
documentation: Created new "Getting Started" manual.
Creation involved removing the overview-manual and replacing it
with the getting-started manual. All links to the string
"&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with
"&YOCTO_DOCS_GS_URL" across the entire YP manual set. I renamed
files used to create the manual with prefixes suited for the
new manual name, which is "Getting Started With Yocto Project".
The style sheet for the new manual needed updating to display the
new .PNG image for the title page. The mega-manual file had to
be updated to include the files. The mega-manual.sed file had
to be updated to include the new manual and not use the overview
manual.
(From yocto-docs rev: 6c7abf9192390121000f577d6c98f259d290d15d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/x32.html')
-rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/x32.html | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/x32.html b/documentation/getting-started/eclipse/html/getting-started/x32.html new file mode 100644 index 0000000000..daffedbeea --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/x32.html | |||
@@ -0,0 +1,75 @@ | |||
1 | <html> | ||
2 | <head> | ||
3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
4 | <title>3.8. x32 psABI</title> | ||
5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
7 | <link rel="home" href="index.html" title="Getting Started With Yocto Project"> | ||
8 | <link rel="up" href="overview-concepts.html" title="Chapter 3. Yocto Project Concepts"> | ||
9 | <link rel="prev" href="other-variables-related-to-commercial-licenses.html" title="3.7.2.2. Other Variables Related to Commercial Licenses"> | ||
10 | </head> | ||
11 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.8. x32 psABI"> | ||
12 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
13 | <a name="x32"></a>3.8. x32 psABI</h2></div></div></div> | ||
14 | <p> | ||
15 | x32 processor-specific Application Binary Interface | ||
16 | (<a class="ulink" href="https://software.intel.com/en-us/node/628948" target="_self">x32 psABI</a>) | ||
17 | is a native 32-bit processor-specific ABI for | ||
18 | <span class="trademark">Intel</span>® 64 (x86-64) | ||
19 | architectures. | ||
20 | An ABI defines the calling conventions between functions in a | ||
21 | processing environment. | ||
22 | The interface determines what registers are used and what the sizes are | ||
23 | for various C data types. | ||
24 | </p> | ||
25 | <p> | ||
26 | Some processing environments prefer using 32-bit applications even | ||
27 | when running on Intel 64-bit platforms. | ||
28 | Consider the i386 psABI, which is a very old 32-bit ABI for Intel | ||
29 | 64-bit platforms. | ||
30 | The i386 psABI does not provide efficient use and access of the | ||
31 | Intel 64-bit processor resources, leaving the system underutilized. | ||
32 | Now consider the x86_64 psABI. | ||
33 | This ABI is newer and uses 64-bits for data sizes and program | ||
34 | pointers. | ||
35 | The extra bits increase the footprint size of the programs, | ||
36 | libraries, and also increases the memory and file system size | ||
37 | requirements. | ||
38 | Executing under the x32 psABI enables user programs to utilize CPU | ||
39 | and system resources more efficiently while keeping the memory | ||
40 | footprint of the applications low. | ||
41 | Extra bits are used for registers but not for addressing mechanisms. | ||
42 | </p> | ||
43 | <p> | ||
44 | The Yocto Project supports the final specifications of x32 psABI | ||
45 | as follows: | ||
46 | </p> | ||
47 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
48 | <li class="listitem"><p> | ||
49 | You can create packages and images in x32 psABI format on | ||
50 | x86_64 architecture targets. | ||
51 | </p></li> | ||
52 | <li class="listitem"><p> | ||
53 | You can successfully build recipes with the x32 toolchain. | ||
54 | </p></li> | ||
55 | <li class="listitem"><p> | ||
56 | You can create and boot | ||
57 | <code class="filename">core-image-minimal</code> and | ||
58 | <code class="filename">core-image-sato</code> images. | ||
59 | </p></li> | ||
60 | <li class="listitem"><p> | ||
61 | RPM Package Manager (RPM) support exists for x32 binaries. | ||
62 | </p></li> | ||
63 | <li class="listitem"><p> | ||
64 | Support for large images exists. | ||
65 | </p></li> | ||
66 | </ul></div> | ||
67 | <p> | ||
68 | </p> | ||
69 | <p> | ||
70 | For steps on how to use x32 psABI, see the | ||
71 | "<a class="link" href="../dev-manual/using-x32-psabi.html" target="_self">Using x32 psABI</a>" | ||
72 | section in the Yocto Project Development Tasks Manual. | ||
73 | </p> | ||
74 | </div></body> | ||
75 | </html> | ||