diff options
author | pancake <pancake@dazo> | 2007-06-02 05:32:43 +0200 |
---|---|---|
committer | pancake <pancake@dazo> | 2007-06-02 05:32:43 +0200 |
commit | 43d8d4591933762cec4e0f72d434aa47311419d3 (patch) | |
tree | a784a16d3debb2590b63af9be904ecaeac767fec /doc | |
parent | f299486ef9ee5531ebee567211eb7861ae7a93bf (diff) | |
download | 0xFFFF-43d8d4591933762cec4e0f72d434aa47311419d3.tar.bz2 |
* Initial import of the offline work of the GUI environment
- Not yet usable, it's just a sketch with glade O:)
- But you can get fun hacking on the source!
* Add deinstall target to the Makefile
* Add INSTALL file for build & install instructions
* Add documentation for local flashing.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/local-flash | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/local-flash b/doc/local-flash new file mode 100644 index 0000000..a09d682 --- /dev/null +++ b/doc/local-flash @@ -0,0 +1,24 @@ +It is possible to flash directly from the device, so this brings the possibility +to completely replace the bootloader flasher by a userland one with extended +features for backuping and recovering data. + +The way to flash is using mtd-utils: + + $ flash_eraseall -j /dev/mtd3 + $ nandwrite -a -p /dev/mtd3 initfs.jffs2 + +This is an specific example plagied from initfs_flasher of bootmenu. + +The '-j' flag says that this is a jffs2 partition. Theorically this +flag is not required for zImage, and the bootloader pieces. + +The '-a' creates the OOB data automatically, and the '-p' flag pads +the data to fill the block. + +These flags are only fine for initfs, so this will be probably wrong +for other pieces. Using the dump functionality you can check if you +have flashed properly every piece inside the device, but keep in mind +that it is dangerous and you can brick your device. + +But feel free to send feedback to provide a full support for local +flashing on n770 and n800. |