Subject: Re: Asking for the stardard test scripts - msg#00021
List: linux.file-systems.yaffs
Hi,
I'm interested in test scripts too.
Regards,
Claudio Lanconelli
Aubrey wrote:
Hi all,
I've ported YAFFS on my system successfully. And I wonder if there are
some startdard test scripts to test it, like power failure testing,
reboot testing, garbage collect testing, etc.
Thanks
-Aubrey
_______________________________________________
yaffs mailing list
yaffs@xxxxxxxxxxxxxxxxxxxxxx
http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: YAFFS2 Development
Jon Masters wrote:
On 12/7/05, Charles Manning <manningc2@xxxxxxxxxxxxx> wrote:
When YAFFS was first written 32MB was big and 128MB was huge :-).
...and 8GB is a little nuts.
Though we are testing 1GBit parts on balloon boards. With 3 devices
fitted we are nearly 1/2 way to the 2GB threshold.
Nick Bane
Jon.
P.S. Just got home after train got stuck so will reply when not using
770 touchscreen from bed :-)
_______________________________________________
yaffs mailing list
yaffs@xxxxxxxxxxxxxxxxxxxxxx
http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
Next Message by Date:
click to view message preview
Re: Squelch mount-time debug messages by default
>
> On Friday 04 November 2005 14:33, Todd Poynor wrote:
> > Modify tracing of yaffs_GutsInitialise entry/exit messages from
> > TRACE_ALWAYS to TRACE_TRACING (assuming this is an intended use of
> that
> > trace flag).
>
> Thanx
>
> Will change this. The current flag usage is a bit unruly.
>
> I might concoct a better trace flag layout at some stage.
>
> BTW:
>
> Does anyone have a simple proc_write that could be hacked/patched
> into
> yaffsfs.c to allow the tracemask to be modified dynamically with
> something
> like:
>
>
> # echo FFFFFFFF > /proc/yaffs
>
> ?
>
> -- Charles
>
Charles,
I have two versions of this type of thing, one simple for the user the
other simple for the programmer. I am attaching the latter. I find it
easier because I can give it the logical name of the flag rather than
it's bit position.
In this one the flags can be set or cleared by echoing the name of the
flag into /proc/yaffs with a '+' or '-':
echo +os-write > /proc/yaffs
It can be set to to all or none using '=', and then flags can be added
or removed:
echo =none+os+write > /proc/yaffs
And you can use numerical values, if you are so inclined (using standard
c format):
echo 0xf00001 > /proc/yaffs
It runs fine on my system, but when I went to add it to the latest
version of Yaffs on the web (as of 9 Dec) I found some differences in
other parts of the file that prevented compilation.
Yeah, I might have gone overboard with this. If you want, I can clean up
the other version and make it available as well.
John
yaffs.patch
Description: Text Data
_______________________________________________
yaffs mailing list
yaffs@xxxxxxxxxxxxxxxxxxxxxx
http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
Previous Message by Thread:
click to view message preview
Asking for the stardard test scripts
Hi all,
I've ported YAFFS on my system successfully. And I wonder if there are
some startdard test scripts to test it, like power failure testing,
reboot testing, garbage collect testing, etc.
Thanks
-Aubrey
Next Message by Thread:
click to view message preview
Asking for the stable version
Hi all,
I want to know if I release the YAFFS in my system for product, Is
there a stable version passed the heavy test? It seems not to be
mentioned on the website. Forgive me if I miss something.
Thanks
-Aubrey