Information/MIPSelFlashROM - Revision history

Jpl: /* Flash ROM analysis */

Jpl — Mon, 12 Oct 2009 14:25:57 GMT

Flash ROM analysis

← Older revision		Revision as of 14:25, 12 October 2009
Line 95:		Line 95:
	mknod /dev/mtd1 c 90 2		mknod /dev/mtd1 c 90 2
	mknod /dev/mtd2 c 90 4		mknod /dev/mtd2 c 90 4
-	mknod /dev/~~mtd2~~ c 90 6	+	mknod /dev/mtd3 c 90 6
	mknod /dev/mtdblock0 b 31 0		mknod /dev/mtdblock0 b 31 0
	mknod /dev/mtdblock1 b 31 1		mknod /dev/mtdblock1 b 31 1

Jpl: /* Flash ROM analysis */

Jpl — Mon, 12 Oct 2009 14:24:35 GMT

Flash ROM analysis

← Older revision		Revision as of 14:24, 12 October 2009
Line 99:		Line 99:
	mknod /dev/mtdblock1 b 31 1		mknod /dev/mtdblock1 b 31 1
	mknod /dev/mtdblock2 b 31 2		mknod /dev/mtdblock2 b 31 2
-	mknod /dev/~~mtdblock2~~ b 31 3	+	mknod /dev/mtdblock3 b 31 3

Jpl at 14:21, 12 October 2009

Jpl — Mon, 12 Oct 2009 14:21:24 GMT

← Older revision		Revision as of 14:21, 12 October 2009
Line 18:		Line 18:
	\|{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}		\|{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}
	\|}		\|}
-	The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match to well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.	+	The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match too well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.

	== Flash ROM analysis ==		== Flash ROM analysis ==

Linuxnotincluded: /* Flash ROM analysis */

Linuxnotincluded — Thu, 30 Aug 2007 21:36:03 GMT

Flash ROM analysis

← Older revision		Revision as of 21:36, 30 August 2007
Line 58:		Line 58:
	\| 90		\| 90
	\| 6		\| 6
-	\| ~~0xbf000000~~	+	\| 0xbfc00000
	\| 0x400000		\| 0x400000
	\| The whole flash.		\| The whole flash.

Linuxnotincluded: /* Flash ROM analysis */

Linuxnotincluded — Sun, 29 Jul 2007 19:08:45 GMT

Flash ROM analysis

← Older revision		Revision as of 19:08, 29 July 2007
Line 30:		Line 30:
	\|style="background:#CCCCCC; color:green"\|'''Major'''		\|style="background:#CCCCCC; color:green"\|'''Major'''
	\|style="background:#CCCCCC; color:green"\|'''Minor'''		\|style="background:#CCCCCC; color:green"\|'''Minor'''
-	\|style="background:#CCCCCC; color:green"\|'''~~End~~'''	+	\|style="background:#CCCCCC; color:green"\|'''Start'''
-	\|style="background:#CCCCCC; color:green"\| '''Size'''	+	\|style="background:#CCCCCC; color:green"\|'''Size'''
	\|style="background:#CCCCCC; color:green"\| '''Function'''		\|style="background:#CCCCCC; color:green"\| '''Function'''
	\|-		\|-
Line 37:		Line 37:
	\| 90		\| 90
	\| 0		\| 0
-	\| ?	+	\| 0xbfc00000
-	\| ?	+	\| 0x040000
-	\| Boot loader (~~bootcode.bin?~~)	+	\| Boot loader (custom version of idt/sim)
	\|-		\|-
	\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd1\|/dev/mtd1]]		\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd1\|/dev/mtd1]]
	\| 90		\| 90
	\| 2		\| 2
-	\| ?	+	\| 0xbfc40000
-	\| ?	+	\| 0x350000
-	\| Stores firmimg.bin (?, vmlinux.gz~~, ramdisk.image.gz~~).	+	\| Stores firmimg.bin (encrypted bzip2 compressed (vmlinux with embedded initrd.gz)).
	\|-		\|-
	\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd2\|/dev/mtd2]]		\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd2\|/dev/mtd2]]
	\| 90		\| 90
	\| 4		\| 4
-	\| ?	+	\| 0xbffc0000
-	\| ?	+	\| 0x040000
	\| Stores configuration files as conf_save.tar.gz (written by ls_flash).		\| Stores configuration files as conf_save.tar.gz (written by ls_flash).
	\|-		\|-
-	\| [[Information/MIPSelFlashROM#~~mtd0~~\|/dev/~~mtdblock0~~]]	+	\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd3\|/dev/mtd3]]
	\| 90		\| 90
		+	\| 6
		+	\| 0xbf000000
		+	\| 0x400000
		+	\| The whole flash.
		+	\|-
		+	\| [[Information/MIPSelFlashROM#mtd0\|/dev/mtdblock0]]
		+	\| 31
	\| 0		\| 0
-	\| ?	+	\|
-	\| ?	+	\|
	\| Block special file version of mtd0.		\| Block special file version of mtd0.
	\|-		\|-
	\| [[Information/MIPSelFlashROM#mtd1\|/dev/mtdblock1]]		\| [[Information/MIPSelFlashROM#mtd1\|/dev/mtdblock1]]
-	\| 90	+	\| 31
-	\| 2	+	\| 1
-	\| ?	+	\|
-	\| ?	+	\|
	\| Block special file version of mtd1.		\| Block special file version of mtd1.
	\|-		\|-
	\| [[Information/MIPSelFlashROM#mtd2\|/dev/mtdblock2]]		\| [[Information/MIPSelFlashROM#mtd2\|/dev/mtdblock2]]
-	\| 90	+	\| 31
-	\| 4	+	\| 2
-	\| ?	+	\|
-	\| ?	+	\|
	\| Block special file version of mtd2.		\| Block special file version of mtd2.
		+	\|-
		+	\| [[Information/MIPSelFlashROM#mtd3\|/dev/mtdblock3]]
		+	\| 31
		+	\| 3
		+	\|
		+	\|
		+	\| Block special file version of mtd3.
	\|}		\|}

Line 81:		Line 95:
	mknod /dev/mtd1 c 90 2		mknod /dev/mtd1 c 90 2
	mknod /dev/mtd2 c 90 4		mknod /dev/mtd2 c 90 4
-	mknod /dev/mtdblock0 b 90 0	+	mknod /dev/mtd2 c 90 6
-	mknod /dev/mtdblock1 b 90 2	+	mknod /dev/mtdblock0 b 31 0
-	mknod /dev/mtdblock2 b ~~90 4~~	+	mknod /dev/mtdblock1 b 31 1
		+	mknod /dev/mtdblock2 b 31 2
		+	mknod /dev/mtdblock2 b 31 3


Line 94:		Line 110:


-	~~there does not seem to be a header like on all other ppc~~-~~boxes + the LS Pro~~.	+	The kernel is compiled with embedded gzip-ed ram disk. The resulting ELF image
-		+	is then compressed using bzip2 and then encrypted. An encrypted header is prepended
-	~~thats why firmimgtool~~ is ~~not able to extract the ramdisk~~.gz and the ~~kernel~~.gz	+	and the result is firmimg.bin.

-	~~maybe the offsets are hardcoded somehow? or maybe this firmimg.bin is scrambled?~~

	=== /dev/mtd2 ===		=== /dev/mtd2 ===

Mindbender: /* /dev/mtd1 */

Mindbender — Thu, 19 Oct 2006 12:08:12 GMT

/dev/mtd1

← Older revision		Revision as of 12:08, 19 October 2006
Line 92:		Line 92:
	=== /dev/mtd1 ===		=== /dev/mtd1 ===
	[[Image:Firmimg_bin_hex_LS2.jpg]]		[[Image:Firmimg_bin_hex_LS2.jpg]]
		+
		+
	there does not seem to be a header like on all other ppc-boxes + the LS Pro.		there does not seem to be a header like on all other ppc-boxes + the LS Pro.

Mindbender: /* /dev/mtd1 */

Mindbender — Thu, 19 Oct 2006 12:07:56 GMT

/dev/mtd1

← Older revision		Revision as of 12:07, 19 October 2006
Line 91:		Line 91:

	=== /dev/mtd1 ===		=== /dev/mtd1 ===
		+	[[Image:Firmimg_bin_hex_LS2.jpg]]
		+	there does not seem to be a header like on all other ppc-boxes + the LS Pro.

		+	thats why firmimgtool is not able to extract the ramdisk.gz and the kernel.gz

		+	maybe the offsets are hardcoded somehow? or maybe this firmimg.bin is scrambled?

	=== /dev/mtd2 ===		=== /dev/mtd2 ===

Ramuk: /* Flash ROM analysis */

Ramuk — Wed, 06 Sep 2006 20:49:14 GMT

Flash ROM analysis

← Older revision		Revision as of 20:49, 6 September 2006
Line 26:		Line 26:
	<center>(all information based on official firmware 2.05):</center>		<center>(all information based on official firmware 2.05):</center>

-	{\| style="width:75%; background:#~~E0FFFF" border="1~~" align=center	+	{\| style="width:75%; background:#DDDDDD;" align=center
-	\|'''Device'''	+	\|style="background:#CCCCCC; color:green"\|'''Device'''
-	\|'''Major'''	+	\|style="background:#CCCCCC; color:green"\|'''Major'''
-	\|'''Minor'''	+	\|style="background:#CCCCCC; color:green"\|'''Minor'''
-	\|'''End'''	+	\|style="background:#CCCCCC; color:green"\|'''End'''
-	\| '''Size'''	+	\|style="background:#CCCCCC; color:green"\| '''Size'''
-	\| '''Function'''	+	\|style="background:#CCCCCC; color:green"\| '''Function'''
	\|-		\|-
	\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd0\|/dev/mtd0]]		\| [[Information/MIPSelFlashROM#.2Fdev.2Fmtd0\|/dev/mtd0]]

Ramuk at 23:53, 1 September 2006

Ramuk — Fri, 01 Sep 2006 23:53:19 GMT

← Older revision		Revision as of 23:53, 1 September 2006
Line 12:		Line 12:
	#Block special files		#Block special files
	#Character special files		#Character special files
-	{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}	+	{\| align=right
		+	\|-
		+	\|{{Postit\|Major number \| The ''major'' number in a special file entry identifies the device driver. Each driver in a Linux or Unix kernel has a number. The major number just selects the driver, e.g. if a serial port driver or a hard disk driver should be associated with the name in the file system}}
		+	\|-
		+	\|{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}
		+	\|}
	The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match to well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.		The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match to well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.

Line 79:		Line 84:
	mknod /dev/mtdblock1 b 90 2		mknod /dev/mtdblock1 b 90 2
	mknod /dev/mtdblock2 b 90 4		mknod /dev/mtdblock2 b 90 4
-
-
-	{{Postit\|Major number \| The ''major'' number in a special file entry identifies the device driver. Each driver in a Linux or Unix kernel has a number. The major number just selects the driver, e.g. if a serial port driver or a hard disk driver should be associated with the name in the file system}}
-

Ramuk at 23:45, 20 July 2006

Ramuk — Thu, 20 Jul 2006 23:45:51 GMT

← Older revision		Revision as of 23:45, 20 July 2006
Line 14:		Line 14:
	{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}		{{Postit\|Minor number \| The ''minor'' number in a special file entry is interpreted individually by a particular device driver. For example a serial driver might use it to compute the I/O address of a UART, or a hard disk driver might use it to address a particular disk on the periphery bus}}
	The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match to well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.		The interfaces of these special files is and was primarily geared at communicating with devices like hard disks, tapes, or terminals. Flash memory, or other 'memory technology' doesn't match to well to the classic device interfaces. For example, writing to a flash device should usually be more controlled to avoid excessive wear and tear of the memory (flash memory allows just a limited number of re-writes). So a particular mtd interface was created in the kernel to support these devices better. In addition, for backward-compatibility with non-mtd-aware software and tools (most are not mtd-aware) the mtd interface was mapped back to the classic block and character special device interfaces. The LinkStation firmware contains the necessary mtd device driver and matching file entries under <tt>/dev</tt>.
-
-	{{Postit\|Major number \| The ''major'' number in a special file entry identifies the device driver. Each driver in a Linux or Unix kernel has a number. The major number just selects the driver, e.g. if a serial port driver or a hard disk driver should be associated with the name in the file system}}
-

	== Flash ROM analysis ==		== Flash ROM analysis ==
Line 82:		Line 79:
	mknod /dev/mtdblock1 b 90 2		mknod /dev/mtdblock1 b 90 2
	mknod /dev/mtdblock2 b 90 4		mknod /dev/mtdblock2 b 90 4
		+
		+
		+	{{Postit\|Major number \| The ''major'' number in a special file entry identifies the device driver. Each driver in a Linux or Unix kernel has a number. The major number just selects the driver, e.g. if a serial port driver or a hard disk driver should be associated with the name in the file system}}