Hi, On Wed, Mar 30, 2011 at 10:11 AM, NamJae Jeon <linkinjeon@xxxxxxxxx> wrote: > usally, bootloader is stored in boot partition. I suggested ioctl to > update bootloader in boot partition not modifing boot partition size. > Maybe I didn't explain myself clearly enough, sorry. The patch I have exposes the boot partitions as block devices and you can read and write to them without affecting the rest of the MMC card. > and moviNAND(samsung) is needed by boot parittion size setting. and > when boot parition size is changed, all user data will be reset, it > will be initial status. > > but iNAND(sandisk) is not needed it. boot partition size is fixed(1MB). > I am unsure what you're talking about. The eMMC 4.41 spec (see 7.2) does not allow changing boot partition size. It is fixed to a certain size, and that size is specified by the BOOT_SIZE_MULTI field in EXT_CSD. For the Toshiba devices I have around me (MMC08G, MMC16G and MMC32G), each boot partition (two total) is 2MB in size. I don't think ioctl for accessing device partitions is a good idea, because the device partitions are just block devices, so they should be exposed as such. For device partitioning, to support create General Purpose partitions (up to 4), an ioctl is probably needed. You could look at "[PATCH resend] mmc: Added ioctl to let userspace apps send ACMDs" by John Calixto which was last send March 17th. That's generic enough to support partitioning (which is a one time programming procedure anyway...so there may be no value of adding a specific ioctl for it, considering how dangerous of an operation it is). A -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
