diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index eb45d99995..96b5469e43 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -632,10 +632,6 @@
You can create packages and images in x32 psABI format on x86_64 architecture targets.
- You can use the x32 psABI support through the meta-x32
- layer on top of the OE-core/Yocto layer.
- The toolchain from the experimental/meta-x32 layer
- is used for building x32 psABI program binaries.
You can successfully build many recipes with the x32 toolchain.
You can create and boot core-image-minimal and
core-image-sato images.
@@ -643,12 +639,12 @@
-
- Future Development and Limitations
+
+ Stabilizing and Completing x32
- As of this Yocto Project release, the x32 psABI kernel and library interfaces
- specifications are not finalized.
+ As of this Yocto Project release, the x32 psABI kernel and library
+ interfaces specifications are not finalized.
@@ -658,8 +654,6 @@
work with and support x32 toolchains.
Enhance RPM Package Manager (RPM) support for x32 binaries.
Support larger images.
- Integrate x32 recipes, toolchain, and kernel changes from
- experimental/meta-x32 into OE-core.
@@ -668,28 +662,8 @@
Using x32 Right Now
- Despite the fact the x32 psABI support is in development state for this release of the
- Yocto Project, you can follow these steps to use the x32 spABI:
+ Follow these steps to use the x32 spABI:
- Add the experimental/meta-x32 layer to your local
- Build Directory.
- You can find the experimental/meta-x32 source repository at
- .
- Edit your conf/bblayers.conf file so that it includes
- the meta-x32.
- Here is an example:
-
- BBLAYERS ?= " \
- /home/nitin/prj/poky.git/meta \
- /home/nitin/prj/poky.git/meta-yocto \
- /home/nitin/prj/poky.git/meta-yocto-bsp \
- /home/nitin/prj/meta-x32.git \
- "
- BBLAYERS_NON_REMOVABLE ?= " \
- /home/nitin/prj/poky.git/meta \
- /home/nitin/prj/poky.git/meta-yocto \
- "
-
Enable the x32 psABI tuning file for x86_64
machines by editing the conf/local.conf like this: