- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. Here is log outport by uclinux
... 0x00200000-0x00d00000 : "romfs/jffs2" 0x00000000-0x00200000 : "loader/kernel" 0x00d00000-0x00e00000 : "User1 configuration" 0x00e00000-0x00f00000 : "User0 configuration" 0x00f00000-0x01000000 : "safe configuration" ... romfs/jffs2: is it romfs or jiffs2? Or romfs formated by jiffs2 ? 2. <drivers>/mtd/maps/altera.c .name = "safe configuration",
.size = 0x200000,
.offset = 0x600000,
.mask_flags = MTD_WRITEABLE, /* force read-only */
why mtd_writeable but /* force read-only */ ? Hehe, I am newbie so the problems confused me.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mountain8848,
> romfs/jffs2: is it romfs or jiffs2? Or romfs formated by jiffs2 ? "romfs/jffs2" is just a name for the partition, nothing more ... it's there only for human consumption ... so the name has absolutely no bearing on what you can or can't put in the partition. Although, it's generally a good idea for the name to describe the _purpose_ of the partion. The author of the mtd map driver is just saying that the partition is _intended_ for use by a "romfs" or "jffs2" filesystem. Perhaps a more generic name would be "filesystem". You can take a look at the code in drivers/mtd/maps for examples. > why MTD_WRITEABLE but /* force read-only */ ? MTD_WRITEABLE is a _mask_, not an enable -- it's a flag indicating what is to be _removed_. To be honest, I never really liked this. Anyway, see: include/linux/mtd/partitions.h and include/mtd/mtd-abi.h Regards, --Scott
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page