summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorpancake <pancake@dazo>2007-06-16 05:52:46 +0200
committerpancake <pancake@dazo>2007-06-16 05:52:46 +0200
commit3728cdea3130c62f3d766df040d2cb85f1e6caa4 (patch)
treee1e683eb758edf0638578c75195c04ec1d35e562 /doc
parentc1d909c41587eb0f4b0581c5be9b70b2b72aefdb (diff)
download0xFFFF-3728cdea3130c62f3d766df040d2cb85f1e6caa4.tar.bz2
* Add new command 'nanddump' for the console shell
* Avoid dumping non-mtd files because writesize = 0 - Properly close the file when failing * Better doc/pieces documentation
Diffstat (limited to 'doc')
-rw-r--r--doc/faq9
-rw-r--r--doc/pieces37
2 files changed, 46 insertions, 0 deletions
diff --git a/doc/faq b/doc/faq
index 1d0b805..5212753 100644
--- a/doc/faq
+++ b/doc/faq
@@ -68,3 +68,12 @@ This file tries to collect a bunch of common questions/answers about flashing
information of different pieces of the firmware. This can be faked, because
you can flash n770 stuff on n800 and viceversa, but it's not recommended
because it wouldn't work :)
+
+
+<b>*) Can I unpack fiasco blobs?</b>
+
+ Actually the fiasco format is not yet supported and not planned in
+ short term. There is no real need for supporting a proprietary
+ format image containing a proprietary system.
+
+ We can just use tarballs containing the desired pieces.
diff --git a/doc/pieces b/doc/pieces
index 2ef2f47..535c35d 100644
--- a/doc/pieces
+++ b/doc/pieces
@@ -4,3 +4,40 @@ Fiasco firmware pieces
The firmware for the maemo devices is composed by a set of pieces containing
the required parts to update the whole system following a partition layout
defined by NOLO on the internal flash memory.
+
+Nokia provides a blob packed with a proprietary format called 'FIASCO'. This
+blob contains the following pieces:
+
+ - omap-nand - only flashable via serial jtag
+ - xloader - first part of nolo
+ - secondary - second part of nolo (usb support and launches kernel)
+ - kernel - the kernel
+ - initfs - initial system that initializes everything and runs rootfs
+ - rootfs - the whole system image
+
+Some of these pieces are versioned to match board specific features
+(mostly xloader and secondary ones).
+
+This format is not supported by 0xFFFF at this moment, but there are no
+plans for doing it in short term. This is because we only need to flash
+separated pieces. We can just distribute tarballs containing the pieces
+and meta information with a whole Free OS for the internet tablets.
+
+To flash an initfs partition and reboot:
+
+ $ 0xFFFF -p initfs%initfs.jffs2 -R
+
+The format of the argument is [piece-type] % [file-name] (% [version-string]).
+
+Pieces can be automatically identified by using the '-I' flag:
+
+ $ 0xFFFF -I initfs.jffs2
+ initfs.jffs2: initfs
+
+You can dump these pieces from the internal memory of the internet
+tablet by using the mtd-utils over /dev/mtd* or just running:
+
+ n770$ 0xFFFF -e /media/mmc1
+
+There is another way for dumping pieces with extra parameters and options,
+read doc/dumping for more information.