Documentation Updates

* Clean up documentation around ext2/cpio
* Split out some of the documentation in the README file into some
  docs/* files
* Moved MAINTAINERS information into the README

Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com>

4 files changed, 30 insertions, 4 deletions

diff --git a/docs/BOOT.sdcard b/docs/BOOT.sdcard
index 488638c9..62897f3c 100644
--- a/docs/BOOT.sdcard
+++ b/docs/BOOT.sdcard
@@ -28,7 +28,7 @@ Use an SD card with partition one in FAT16 format.
 
 Copy the following to the SD card partition one:
         * Kernel:     uImage
-        * Root FS:    core-image-minimal-<machine name>.ext2.gz.u-boot
+        * Root FS:    core-image-minimal-<machine name>.cpio.gz.u-boot
         * Devicetree: uImage-<machine name>.dtb
 
 Also create the file "uEnv.txt" on the SD card parition one, with the following
@@ -38,7 +38,7 @@ correct name for you machine/system.
 
         kernel_image=uImage
         devicetree_image=uImage-<machine name>.dtb
-        ramdisk_image=core-image-minimal-<machine name>.ext2.gz.u-boot
+        ramdisk_image=core-image-minimal-<machine name>.cpio.gz.u-boot
 
 Alternatively you can use the default names for the images, rename them
 according to below and copy them onto partition one. Doing this removes the need
@@ -54,7 +54,7 @@ board. (Ensure the board is configured via the MIO's for SD Boot).
 Booting the Kernel (with mmcblk/SD card rootfs)
 -----------------------------------------------
 Use an SD card with partition one in FAT16 format, and an additional partition
-for the root filesystem (formatted as EXT2).
+for the root filesystem (formatted as EXT2/3/4).
 
 Copy the following to the SD card partition one:
         * Kernel:     uImage
diff --git a/docs/BOOT.tftp b/docs/BOOT.tftp
index 17d7e3a4..de3a70ad 100644
--- a/docs/BOOT.tftp
+++ b/docs/BOOT.tftp
@@ -7,7 +7,7 @@ Note: This boot flow requires a TFTP server.
 Boot your system into U-Boot, using an alternative boot method (e.g. JTAG, SD).
 
 Place the following images into the root of the TFTP server directory:
-        * core-image-minimal-<machine name>.ext2.gz.u-boot (RootFS)
+        * core-image-minimal-<machine name>.cpio.gz.u-boot (RootFS)
         * linux.bin.ub or uImage (Linux Kernel)
         * <kernel binary>-<machine name>.dtb (DTB)
 
diff --git a/docs/Rootfs b/docs/Rootfs
new file mode 100644
index 00000000..656b4b36
--- /dev/null
+++ b/docs/Rootfs
@@ -0,0 +1,11 @@
+
+Configuring Additional RootFS Output Images
+===========================================
+
+To configure the build or the machine to output additional rootfs image types
+the IMAGE_FSTYPES variable can be overridden or appended to.
+
+e.g. Add ext2 and ext2.gz.u-boot image types to the local.conf
+
+        IMAGE_FSTYPES += "ext2 ext2.gz.u-boot"
+
diff --git a/docs/Toolchain b/docs/Toolchain
new file mode 100644
index 00000000..7e8d313b
--- /dev/null
+++ b/docs/Toolchain
@@ -0,0 +1,15 @@
+
+Configuring External Toolchain
+==============================
+
+In order to build with an external toolchain some additional configuration must
+be set in the build environments local.conf. First configure the use of an
+external toolchain, including the location to the toolchain:
+
+        TCMODE = "external-xilinx"
+        EXTERNAL_TOOLCHAIN = "<path to toolchain>"
+
+WARNING: There is a known issue with the MicroBlaze Linux toolchain provided by
+XSDK 2013.3 where certain shift instructions are not generated correctly, avoid
+using this toolchain. Use the newer XSDK 2013.4 or PetaLinux 2013.10 toolchains.
+