Mike, Start here: http://wiki.openwrt.org/doc/start. Scroll down to "Technical References". When you find the missing answers to your questions, can you add an article there?
Thanks, -K- On 10/14/10 11:58 PM, W. Michael Petullo wrote:
I have some MTD-related questions about OpenWrt on my WRT160NL. /proc/mtd shows the layout of MTD. In my case, dev: size erasesize name mtd0: 00040000 00010000 "u-boot" mtd1: 00130000 00010000 "kernel" mtd2: 00670000 00010000 "rootfs" mtd3: 002f0000 00010000 "rootfs_data" mtd4: 00010000 00010000 "nvram" mtd5: 00010000 00010000 "art" mtd6: 007a0000 00010000 "firmware" Where does this come from? That is, is it specific to a device and set up by the vendor? Or, does OpenWrt influence the layout? How does U-Boot work? For example, I use mtd to write an image to "firmware." Does OpenWrt build this image in the way that Linksys' U-Boot configuration expects? Or is U-Boot's configuration rewritten by the OpenWrt install process? Where is the best source for documentation on TRX? What part of the system understands TRX? U-Boot? If I write an image to "firmware" using mtd, then how does "kernel," "rootfs," etc. get filled? Is this done by U-Boot? What is "rootfs_data," "nvram" and "art?"
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel