From: Artem Bityutskiy <dedekind@infradead.org>
To: Aubrey <aubreylee@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mount costs too long
Date: Fri, 10 Nov 2006 18:08:18 +0200 [thread overview]
Message-ID: <1163174898.3925.13.camel@sauron> (raw)
In-Reply-To: <6d6a94c50611100648g87770a0qb723fad11fa65cd8@mail.gmail.com>
On Fri, 2006-11-10 at 22:48 +0800, Aubrey wrote:
> I got a clue from YAFFS mailing list, this is a known issue on 2.6.18 kernels.
> It is caused by the MTD layer rework and corresponding yaffs-mtd layer
> modifications. Namely, an additional translation had to be implemented
> for OOB area for 512b page chips.
Is it possible to describe this in more details? And why YAFFS people do
not fix this?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-10 16: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 [this message]
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
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=1163174898.3925.13.camel@sauron \
--to=dedekind@infradead.org \
--cc=aubreylee@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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