On Monday 30 April 2007, Meher wrote:
> Then application will not even bother if he is a USB
> device or on board flash and just do the normal read/write from
> /dev/flashd?
"flashd" is some wierd new convention it seems. There are two basic
models for flash memory on Linux.
- The "native" one uses the MTD code, so you'd see /dev/mtdblock3
or somesuch (depending on what devices and partitions exist).
That basically works with JFFS2 and similar filesystems designed
to be flash-aware.
- Then there are "bridged" ones using USB, IDE, MMC/SD and so forth
to connect to some controller that presents a block device model
and handles the wear-leveling itself. Those can use filesystems
like VFAT or EXT3.
Now in *EITHER CASE* the application should not normally be writing
directly to the /dev/ block device ... it should be using filesystem
code. There are exceptions like "mtools" ... and lots of reasons to
avoid using them.
- Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
