Reset poky to before our libpam hacks
Things got a bit out of synch with openbmc-config due to the libpam
issues and the migration from the meta-* layers.
Revert the two previous commits and then put the latest poky in with the
libpam revert and get openbmc-config right again.
Revert "Revert "libpam: update 1.3.1 -> 1.5.1""
This reverts commit 87ddd3eab4df68e624b5350ccaab28b3b97547c0.
Revert "poky: subtree update:796be0593a..10c69538c0"
This reverts commit c723b72979bfac6362509cf1fe086900f6641f28.
Change-Id: I3a1f405193aee6a21fe0cd24be9927c143a23d9a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/poky/documentation/ref-manual/classes.rst b/poky/documentation/ref-manual/classes.rst
index a152dca..5a30ce3 100644
--- a/poky/documentation/ref-manual/classes.rst
+++ b/poky/documentation/ref-manual/classes.rst
@@ -278,7 +278,7 @@
This class is used to give a minor performance boost during the build.
However, using the class can lead to unexpected side-effects. Thus, it
is recommended that you do not use this class. See
-https://ccache.samba.org/ for information on the C/C++ Compiler
+http://ccache.samba.org/ for information on the C/C++ Compiler
Cache.
.. _ref-classes-chrpath:
@@ -1374,36 +1374,36 @@
``kernel-fitimage.bbclass``
===========================
-The ``kernel-fitimage`` class provides support to pack a kernel image,
+The ``kernel-fitimage`` class provides support to pack a kernel Image,
device trees and a RAM disk into a single FIT image. In theory, a FIT
-image can support any number of kernels, RAM disks and device trees.
+image can support any number of kernels, RAM disks and device-trees.
However, ``kernel-fitimage`` currently only supports
limited usescases: just one kernel image, an optional RAM disk, and
-any number of device trees.
+any number of device tree.
To create a FIT image, it is required that :term:`KERNEL_CLASSES`
-is set to include "kernel-fitimage" and :term:`KERNEL_IMAGETYPE`
+is set to "kernel-fitimage" and :term:`KERNEL_IMAGETYPE`
is set to "fitImage".
-The options for the device tree compiler passed to ``mkimage -D``
+The options for the device tree compiler passed to mkimage -D feature
when creating the FIT image are specified using the
:term:`UBOOT_MKIMAGE_DTCOPTS` variable.
Only a single kernel can be added to the FIT image created by
``kernel-fitimage`` and the kernel image in FIT is mandatory. The
-address where the kernel image is to be loaded by U-Boot is
+address where the kernel image is to be loaded by U-boot is
specified by :term:`UBOOT_LOADADDRESS` and the entrypoint by
:term:`UBOOT_ENTRYPOINT`.
Multiple device trees can be added to the FIT image created by
``kernel-fitimage`` and the device tree is optional.
-The address where the device tree is to be loaded by U-Boot is
+The address where the device tree is to be loaded by U-boot is
specified by :term:`UBOOT_DTBO_LOADADDRESS` for device tree overlays
and by :term:`UBOOT_DTB_LOADADDRESS` for device tree binaries.
Only a single RAM disk can be added to the FIT image created by
``kernel-fitimage`` and the RAM disk in FIT is optional.
-The address where the RAM disk image is to be loaded by U-Boot
+The address where the RAM disk image is to be loaded by U-boot
is specified by :term:`UBOOT_RD_LOADADDRESS` and the entrypoint by
:term:`UBOOT_RD_ENTRYPOINT`. The ramdisk is added to FIT image when
:term:`INITRAMFS_IMAGE` is specified.
@@ -2581,7 +2581,7 @@
:term:`SYSTEMD_BOOT_TIMEOUT` variables.
You can also see the `Systemd-boot
-documentation <https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/>`__
+documentation <http://www.freedesktop.org/wiki/Software/systemd/systemd-boot/>`__
for more information.
.. _ref-classes-terminal: