From: Ilguiz Latypov <ilatypov@infradead.org>
To: linux-mtd@lists.infradead.org
Subject: Re: DiskOnChip 2000 TSOP bad blocks table
Date: Thu, 20 Nov 2003 16:29:20 -0500 [thread overview]
Message-ID: <20031120212920.GA8274@ei.homeip.net> (raw)
In-Reply-To: <7iu14yeq4s.fsf@thor.cctechnol.com>
Hello Al,
On Thu, Nov 20, 2003 at 02:33:55PM -0600, Al Cousson wrote:
> 2. Does doc_loadbios need to be updated to work on the DiskOnChip
> 2000 TSOP?
I am not sure if the current patch to GRUB recognizes INFTL. I know
that the NFTL block access layer did work. The beginning of the NFTL
layer must not be overwritten by the GRUB firmware. Once you burned the
firmware, you may need to re-format the rest of the chip. The size of
the GRUB firmware rounded to the next erase sector boundary could be
given to the format utility as the start offset for the NFTL layer.
--
Ilguiz Latypov
next prev parent reply other threads:[~2003-11-20 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 20:33 DiskOnChip 2000 TSOP bad blocks table Al Cousson
2003-11-20 21:29 ` Ilguiz Latypov [this message]
2003-11-21 19:39 ` David Dillow
2003-12-03 10:21 ` 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=20031120212920.GA8274@ei.homeip.net \
--to=ilatypov@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