From: Greg Ungerer <gerg@snapgear.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Roy Lauer <rlaor@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problems with DOC Millennium Plus
Date: Thu, 05 Feb 2004 16:54:16 +1000 [thread overview]
Message-ID: <4021E898.2080901@snapgear.com> (raw)
In-Reply-To: <1075890631.5699.3.camel@lapdancer.baythorne.internal>
David Woodhouse wrote:
> If your mailer is broken and loses References: headers, get a real one.
> Don't just remove 'Re:' from your subject line to get around the
> filters.
>
> On Wed, 2004-02-04 at 02:12 -0800, Roy Lauer wrote:
>
>>>The DiskOnChip Millennium Plus uses INFTL not NFTL.
>>
>>You should be very
>>
>>>careful using the current INFTL code -- it does not
>>
>>observe the Bad Block Table.
How did you format the DoC INFTL?
Did you use the M-Systems tools, or a modified nftl_format
under Linux?
>>What does it mean?
>>Does it mean that practically the current INFTL code
>>is unusable with the DiskOnChip Millennium Plus?
>>
>>The DOC is recognized correctly but I keep getting
>>"corrupt block" errors (please see the log below).
>
>
> It does indeed look like it's trying to erase blocks which are actually
> bad -- which it should have _known_ are bad if it had been able to read
> the BBT.
>
> We really do need to implement support for reading the BBT.
I have a modified nftl_format code that reads the BBT when
doing the INFTL formating, and thus avoids the appropriate
bad blocks at format time. Now we just need the inftlmount
code to parse it as well.
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
prev parent reply other threads:[~2004-02-05 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 10:12 Problems with DOC Millennium Plus Roy Lauer
2004-02-04 10:30 ` David Woodhouse
2004-02-05 6:54 ` Greg Ungerer [this message]
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=4021E898.2080901@snapgear.com \
--to=gerg@snapgear.com \
--cc=dwmw2@infradead.org \
--cc=rlaor@yahoo.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