r mmc in below link
> https://lkml.org/lkml/2013/4/1/292
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
buffer, and then copying that to RAM. And the second part is
something people sometimes do with DMA, AFAIU.
If your HW supports this, sure the MTD framework can be re-worked. Or
you may write your own 'mtd->_read()' / 'mtd->_write()' implementation.
--
Best Regards,
Artem Bit
ddir + stat. Besides, this stuff tend to change more
often than the data, so mixing it with the data in the same eraseblock
is not smart.
3. context = parent inode number for all the stuff belonging to xattrs.
We do something similar in UBIFS.
--
Best Regards,
Artem Bityutskiy
signature.asc
De
re might not even be a guarantee that those flash devices will all
> have the same characteristics. So to say that making this tuning at
> mkfs time is probably not the best strategy.
Good point. But we can always set the eraseblock size in the superblock
to -1 which would mean "unknow
identifiers like
"get_context()". This would hurt readability. It is fine to use it
withing the UFS-specific code, but not globally withing the kernel code.
I do not really have good name candidates, but even "ufscontext" is
already better than just "context". Or "