summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorpancake <pancake@dazo>2007-04-20 21:00:12 +0200
committerpancake <pancake@dazo>2007-04-20 21:00:12 +0200
commit196f1f7abbb896b84bbbb7a813e9d6641e162fc1 (patch)
treeb72b4afb8fa3f104adb3317d3f94340e32198a36 /doc
parent300635ad8f8c5bdb5c50fc95f1c456ea7cc45151 (diff)
download0xFFFF-196f1f7abbb896b84bbbb7a813e9d6641e162fc1.tar.bz2
* Do not strip the initfs.jffs2 image, it is only 2MB
* Some fixups on the doc/dumping documentation
Diffstat (limited to 'doc')
-rw-r--r--doc/dumping9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/dumping b/doc/dumping
index 0017a33..3f22a82 100644
--- a/doc/dumping
+++ b/doc/dumping
@@ -25,8 +25,8 @@ pieces at certains offsets of the device internal memory.
<b>Technical details:</b>
- * The internal flash memory is exposed to the system as MTD devices. So it's
- * possible to dump the individual sections of a flashed firmware.
+ * The internal flash memory is exposed to the system as MTD devices.
+ * Is possible to dump the individual sections of a flashed firmware.
*
* READ src/dump.c for detailed information.
@@ -40,6 +40,9 @@ pieces at certains offsets of the device internal memory.
mtd2 - starts with NOLO img\x5c\x13 and \x00 padding
0x00800 - zImage
- mtd3 - rootfs.jffs2 (20M) aka 0x200000 vs 0x3900000
+ > NOLO is a four byte marker, next four bytes
+ > can vary since it is kernel image size
+
+ mtd3 - initfs.jffs2 (2M) aka 0x200000 vs 0x3900000
mtd4 - rootfs.jffs2 (a fucking copy of the above rootfs?)