From: Claudio Lanconelli <lanconelli.claudio@eptar.com>
To: linux-mtd@lists.infradead.org
Cc: Vitaly Wool <vwool@ru.mvista.com>
Subject: Re: mount costs too long
Date: Fri, 10 Nov 2006 18:01:42 +0100 [thread overview]
Message-ID: <4554B076.5010705@eptar.com> (raw)
In-Reply-To: <4554AA07.5020204@ru.mvista.com>
Vitaly Wool wrote:
> B/c due to the MTD layer rework, there's no way now to use custom
> oobinfo in yaffs.
> Therefore, as yaffs1 presumes the SmartMedia OOB layout one can either
> read/write raw OOB but that will most probably break the bad block
> handling, or implement a small shim layer putting spare OOB area into
> SmartMedia OOB layout or back. Any other way will result in
> incompatibility with the older version of yaffs1.
>
Is there a way to specify SmartMedia OOB layout in the board
driver?
Also ssfdc.c needs SmartMedia OOB layout to work.
Cheers,
Claudio Lanconelli
next prev parent reply other threads:[~2006-11-10 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 7:05 mount costs too long Aubrey
2006-11-10 11:56 ` Josh Boyer
2006-11-10 14:48 ` Aubrey
2006-11-10 16:08 ` Artem Bityutskiy
2006-11-10 16:15 ` Vitaly Wool
2006-11-10 16:26 ` Artem Bityutskiy
2006-11-10 16:34 ` Vitaly Wool
2006-11-10 17:01 ` Claudio Lanconelli [this message]
2006-11-10 17:05 ` Vitaly Wool
2006-11-10 17:15 ` Artem Bityutskiy
2006-11-11 14:11 ` Aubrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4554B076.5010705@eptar.com \
--to=lanconelli.claudio@eptar.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vwool@ru.mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox