From: Greg Ungerer <gerg@snapgear.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Kalev Lember <kalev@colleduc.ee>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad blocks
Date: Fri, 02 Apr 2004 10:14:19 +1000 [thread overview]
Message-ID: <406CB05B.5030000@snapgear.com> (raw)
In-Reply-To: <1080830176.24117.1858.camel@hades.cambridge.redhat.com>
David Woodhouse wrote:
> On Thu, 2004-04-01 at 17:06 +0300, Kalev Lember wrote:
>>I am going to use DOC Millennium Plus and I do not want to use M-Systems
>>propietary kernel modules.
>>Having read the mailing list archives I have some questions. Does current
>>INFTL code support bad block handling? Without that I would say it is
>>virtually useless. Am I correct?
>
>
> It doesn't, and you're probably correct, yes.
>
> This is fairly high up on my TODO list but keeps getting preempted by
> RealWork(tm). Are you volunteering? It shouldn't be too hard.
Yeah, high on my todo list as well. But I am not going to
get to it any time soon. It should be quite simple to do.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a CyberGuard Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2004-04-02 0:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:06 Bad blocks Kalev Lember
2004-04-01 14:36 ` David Woodhouse
2004-04-02 0:01 ` patch for AMD am29dl800b David Updegraff
2004-04-02 5:57 ` David Woodhouse
2004-04-02 13:30 ` David Updegraff
2004-04-02 13:39 ` David Woodhouse
2004-04-02 0:14 ` Greg Ungerer [this message]
2004-04-04 11:16 ` Bad blocks Kalev Lember
-- strict thread matches above, loose matches on Subject: below --
2005-04-26 20:33 Bad Blocks Eddie Dawydiuk
2005-04-26 22:43 ` Charles Manning
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=406CB05B.5030000@snapgear.com \
--to=gerg@snapgear.com \
--cc=dwmw2@infradead.org \
--cc=kalev@colleduc.ee \
/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