This means we are supporting two separate file system on our embedded device, one (YAFF/JFFS) for read/write operation on flash and other (FAT) to have read/write operation on the SD/MMC card i.e multi media operations.

If yes, then for the user space application is not it confusing to have two separate read/write calls api ?

--
Gaur

On Mon, Sep 29, 2008 at 11:33 AM, Peter Barada <peterb@logicpd.com> wrote:
On Mon, 2008-09-29 at 11:26 -0700, Yogesh Gaur wrote:
Hello everybody,

I am new to this group and have just start to look the yaff code and docs, I have some of the basic doubts about the whole system on which Linux YAFF running.

As last week Google phone has been launched with lot of fanfare, it has linux as it's OS, my doubt is if my phone is supporting the SD card (which it of course does) then how the linux able to read/write to the SD card as generally SD card have been formatted in the FAT filesystem (my assumption in thinking that most of the users would transfer the media files from their to the windows PC's).

What is the interface in between the YAFF file system and the SD driver through which file system is able to detect the SD card and do corresponding operation of read/write?

None. The SD card driver presents block calls to the FAT filesystem code.  As such YAFFS is not involved.


Sorry for asking this basic question but just due to curiosity I am asking this.

Thanks,
Gaur
_______________________________________________
yaffs mailing list
yaffs@lists.aleph1.co.uk
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
--
Peter Barada <peterb@logicpd.com>