From: 김영호 <yhkim@openers.co.kr>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: problem with ftl_format
Date: Mon, 18 Feb 2002 19:25:20 +0900 [thread overview]
Message-ID: <03d101c1b866$9125c0b0$126171d3@caesar> (raw)
No, it just print error message and return
----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "±e¿μE￡" <yhkim@openers.co.kr>
Cc: <linux-mtd@lists.infradead.org>
Sent: Monday, February 18, 2002 6:49 PM
Subject: Re: problem with ftl_format
>
> yhkim@openers.co.kr said:
> > I am building MTD/FTL driver on NAND Flash. When formating the mtd(/
> > dev/mtd0) with ftl_format, format operation stops proceeding becaus of
> > a bad block. why one bad block leads format operation to fail? Anybody
> > could direct me how to handle this problem?
> >
>
> Er, make ftl_format mark the block bad and continue?
>
> --
> dwmw2
next reply other threads:[~2002-02-18 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 10:25 김영호 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 8:36 problem with ftl_format 김영호
2002-02-18 9:49 ` David Woodhouse
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='03d101c1b866$9125c0b0$126171d3@caesar' \
--to=yhkim@openers.co.kr \
--cc=dwmw2@infradead.org \
--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