Thanx Nick
I'll do what you suggest here. That should give people the fast stuff but
still not break people who are not yet up to date.
I will doc what I want to do in YAFFS2 (and why) including ECC placement etc
and ask for input.
Thanx again all...
-- CHarles
-----Original Message-----
From: Nick Bane [
mailto:nick@cecomputing.co.uk]
Sent: Monday, 25 November 2002 12:00 p.m.
To: Charles Manning;
tglx@linutronix.de; yaffs list
Cc: Jeffrey Lim;
manningc2@actrix.gen.nz
Subject: Re: Latest CVS
> My current stuff is built on 2.4.18 (we used that as a springboard for
> YAFFS). Maybe it is time to move and apply mtd patches. Suggestions? I am
a
> bit concerned that moving too fast on mtd might mean that YAFFS would then
> require new features and lose backward compatibility. Thoughts?
>
The newest mtd in cvs seems ideally suited to yaffs and it would be a pity
to not use it. My only problem with the newest mtd api is that it isn't in a
mainstream arm kernel yet. 2.4.19-rmk4 doesn't use the latest read_ecc and
write_ecc api. Can someone (Thomas?) send a patch to Russell for him to
build into rmk5 or something? He was complaining a while back that people
don't feed him stable patches for him to include.
It could be a compile-time option for yaffs with a CONFIG_OLD_MTD_COMPAT
switch that would do it the slow reliable existing way.
Nick
---------------------------------------------------------------------------------------
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.