> >
> > I think if you want to reserve the functionality to use the eccstatus in
> > readChunkFromNAND then we can go to the other solution of copying (spare
+
> > eccres1 + eccres2) in nandmtd_ReadChunkFromNand and do away with
tmpSpare.
> > But we have to be very careful for all functions calling
> > nandmtd_ReadChunkFromNand to ensure that it passes a yaffs_Spare
> > buffer that
> > is large enough to accomodate the extra ints. Somebody in the future
may
> > forget this fact since usually yaffs_Spare is defined as
> > YAFFS_BYTES_PER_SPARE bytes.
> >
All that is true.
However, nandmtd_RedChunkFromNAND only reports YAFFS_OK and YAFFS_FAIL.
Could we not add YAFFS_CORRECTED as an additional response?
It would mean that we are still replying with !=YAFFS_OK and adds more
information.
Nick
-------------------------------------------
Nick Bane
Cambridge, UK.
+44(0)1954 719270
---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (
www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by
sending an email to
yaffs-request@toby-churchill.org with the text "unsubscribe"
(without the quotes) as the subject.
(text/plain)