Patchwork [2/2] rpi: rename board folder for consistency

login
register
mail settings
Submitter mathieu benoit
Date May 10, 2013, 2:40 p.m.
Message ID <1368196811-6631-1-git-send-email-mathieu.benoit@savoirfairelinux.com>
Download mbox | patch
Permalink /patch/242999/
State Superseded
Headers show

Comments

mathieu benoit - May 10, 2013, 2:40 p.m.
All the Raspberry Pi files (packages and config) are prefix with "rpi",
so rename the board directory to "rpi" for consistency.

Signed-off-by: Mathieu Benoit <mathieu.benoit@savoirfairelinux.com>
---
 board/raspberrypi/readme.txt | 108 -------------------------------------------
 board/rpi/readme.txt         | 108 +++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 108 insertions(+), 108 deletions(-)
 delete mode 100644 board/raspberrypi/readme.txt
 create mode 100644 board/rpi/readme.txt

Patch

diff --git a/board/raspberrypi/readme.txt b/board/raspberrypi/readme.txt
deleted file mode 100644
index 3f2ee37..0000000
--- a/board/raspberrypi/readme.txt
+++ /dev/null
@@ -1,108 +0,0 @@ 
-RaspberryPi
-
-Intro
-=====
-
-To be able to use your RaspberryPi board with the images generated by
-Buildroot, you have a prior choice to make, will you use:
-
- * Volatile rootfs in RAM (the rootfs is an initramfs) or
- * Persistent rootfs on the SDCard
-
-Also, a good source of information is http://elinux.org/R-Pi_Hub
-
-How to build it
-===============
-
-You need to use the rpi_defconfig, to do so:
-
- $ make rpi_defconfig
-
-If Volatile rootfs
-------------------
-
-Then, you need to select the kind of images you want:
-
- $ make menuconfig
-
- * Select "Filesystem images"
- * Select "initial RAM filesystem linked into linux kernel"
-
-Build
------
-
- $ make
-
-And take a coffee
-
-### What is generated
-
-After building, you should obtain this tree:
-
-    output/images/
-    +-- rootfs.tar
-    +-- rpi-firmware
-    |   +-- bootcode.bin
-    |   +-- config.txt
-    |   +-- fixup_cd.dat
-    |   +-- fixup.dat
-    |   +-- start_cd.elf
-    |   `-- start.elf
-    `-- zImage
-
-Note for Volatile: rootfs.tar will only be there if you kept
-"tar the root filesystem" option selected in "Filesystem images".
-
-Prepare you SDCard
-==================
-
-For more information, visit
-http://elinux.org/RPi_Advanced_Setup#Advanced_SD_card_setup
-
-In summary, your SDCard must have first partition in fat32 and marked bootable.
-
-If Persistent rootfs, 50Mo is enough memory for the boot fat32 partition.
-Create another partition, like ext4, for the root.
-
-Mount partition:
-
- $ sudo mount /dev/sdX1 /mnt/mountpointboot
-
- $ sudo mount /dev/sdX2 /mnt/mountpointroot
-
-Note: You can create any number of partitions you desire, the only requirement
-is that the first partition must be using fat32 and be bootable.
-
-Where should the binaries be copied on the SDCard
--------------------------------------------------
-
-At the root of the boot partition,
-the RaspberryPi must find the following files:
-
- * bootcode.bin
- * config.txt		(optional)
- * fixup_cd.dat
- * fixup.dat
- * start_cd.elf
- * start.elf
- * zImage
-
-For example: (Assuming mountpointboot is a directory and exists)
-
- $ cp ./rpi-firmware/* /mnt/mountpointboot/
-
- $ cp ./zImage /mnt/mountpointboot/zImage.img
-
-Note: The default name is kernel.img.
-Actually, the name is zImage and it's define in the file config.txt like:
-kernel=zImage
-
-### If Persistent rootfs partition
-
-The second partition will contain your rootfs.
-Simply extract (as root!) the contents of the rootfs.tar archive
-into this partition.
-
-For example: (Assuming mountpointroot is a directory and exists)
-
- $ sudo tar xf rootfs.tar -C /mnt/mountpointroot
diff --git a/board/rpi/readme.txt b/board/rpi/readme.txt
new file mode 100644
index 0000000..3f2ee37
--- /dev/null
+++ b/board/rpi/readme.txt
@@ -0,0 +1,108 @@ 
+RaspberryPi
+
+Intro
+=====
+
+To be able to use your RaspberryPi board with the images generated by
+Buildroot, you have a prior choice to make, will you use:
+
+ * Volatile rootfs in RAM (the rootfs is an initramfs) or
+ * Persistent rootfs on the SDCard
+
+Also, a good source of information is http://elinux.org/R-Pi_Hub
+
+How to build it
+===============
+
+You need to use the rpi_defconfig, to do so:
+
+ $ make rpi_defconfig
+
+If Volatile rootfs
+------------------
+
+Then, you need to select the kind of images you want:
+
+ $ make menuconfig
+
+ * Select "Filesystem images"
+ * Select "initial RAM filesystem linked into linux kernel"
+
+Build
+-----
+
+ $ make
+
+And take a coffee
+
+### What is generated
+
+After building, you should obtain this tree:
+
+    output/images/
+    +-- rootfs.tar
+    +-- rpi-firmware
+    |   +-- bootcode.bin
+    |   +-- config.txt
+    |   +-- fixup_cd.dat
+    |   +-- fixup.dat
+    |   +-- start_cd.elf
+    |   `-- start.elf
+    `-- zImage
+
+Note for Volatile: rootfs.tar will only be there if you kept
+"tar the root filesystem" option selected in "Filesystem images".
+
+Prepare you SDCard
+==================
+
+For more information, visit
+http://elinux.org/RPi_Advanced_Setup#Advanced_SD_card_setup
+
+In summary, your SDCard must have first partition in fat32 and marked bootable.
+
+If Persistent rootfs, 50Mo is enough memory for the boot fat32 partition.
+Create another partition, like ext4, for the root.
+
+Mount partition:
+
+ $ sudo mount /dev/sdX1 /mnt/mountpointboot
+
+ $ sudo mount /dev/sdX2 /mnt/mountpointroot
+
+Note: You can create any number of partitions you desire, the only requirement
+is that the first partition must be using fat32 and be bootable.
+
+Where should the binaries be copied on the SDCard
+-------------------------------------------------
+
+At the root of the boot partition,
+the RaspberryPi must find the following files:
+
+ * bootcode.bin
+ * config.txt		(optional)
+ * fixup_cd.dat
+ * fixup.dat
+ * start_cd.elf
+ * start.elf
+ * zImage
+
+For example: (Assuming mountpointboot is a directory and exists)
+
+ $ cp ./rpi-firmware/* /mnt/mountpointboot/
+
+ $ cp ./zImage /mnt/mountpointboot/zImage.img
+
+Note: The default name is kernel.img.
+Actually, the name is zImage and it's define in the file config.txt like:
+kernel=zImage
+
+### If Persistent rootfs partition
+
+The second partition will contain your rootfs.
+Simply extract (as root!) the contents of the rootfs.tar archive
+into this partition.
+
+For example: (Assuming mountpointroot is a directory and exists)
+
+ $ sudo tar xf rootfs.tar -C /mnt/mountpointroot