OOB questions

[Ravi Vasarla]

Hi,

Yes JAFFS2 or YAFFS2 will require the ability to read or write in OOB
bytes, refer also yaffs2 call flow for read and write operations. It is
upto the driver or file system how it is identifying the OOB area and
doing the operations so that file system should aware of actual read or
write size in NAND in below it is like 2048 byte + 16 Bytes of oob area.
 While doing the raw block device read or write operation, in that case
it is not required to send the OOB details. Also there is no such
requirement for OOB and non OOB happens independently.

Regards,
Ravi 

-----Original Message-----
From: linux-mtd-bounces at lists.infradead.org
[mailto:linux-mtd-bounces at lists.infradead.org] On Behalf Of Curt Scott
Sent: Tuesday, October 07, 2008 12:11 AM
To: linux-mtd at lists.infradead.org
Subject: OOB questions

Hi,

I am writing a MTD NAND (2K page) driver module for Linux 2.6.23. 
My NAND hardware controller performs all the ECC control under-the-hood.
Although is has OOB bytes available there are some limitaitions...

L1.) Page data and OOB data must be written at the same time.
L2.) OOB data is limited to 16 bytes / page (of a 2k page).

I have some questions about the OOB requirements for MTD/JFFS2 combo.

Q1.) Does MTD/JFFS2 require the ability to read/write OOB bytes?  
     Or can the system be set up operate with no OOB available?
Q2.) Is it a requirement for OOB and non-OOB writes to happen
independently?

thank you for you help,
Curt

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
SASKEN BUSINESS DISCLAIMER
-------------------------
This message may contain confidential, proprietary or legally privileged information. In 
case you are not the original intended Recipient of the message, you must not, directly or 
indirectly, use, Disclose, distribute, print, or copy any part of this message and you are 
requested to delete it and inform the sender. Any views expressed in this message are 
those of the individual sender unless otherwise stated. Nothing contained in this message 
shall be construed as an offer or acceptance of any offer by Sasken Communication 
Technologies Limited ("Sasken") unless sent with that express intent and with due 
authority of Sasken. Sasken has taken enough precautions to prevent the spread of 
viruses. However the company accepts no liability for any damage caused by any virus 
transmitted by this email