public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Saul Thurrowgood <saul@cvs.anu.edu.au>
To: linux-mtd@lists.infradead.org
Subject: DOC 2000 driver (NFTL) in kernel 2.4.7
Date: Wed, 01 Aug 2001 13:46:24 +1000	[thread overview]
Message-ID: <3B677B90.B2E244BD@cvs.anu.edu.au> (raw)
In-Reply-To: E15RXGo-00058Q-00@pentafluge.infradead.org

> 3) (and this is the show stopper) The NFTL driver is not able to find a
> boot record on the DOC. This is strange because I'm actually booting
> from the DOC.
>
> The previous configuration used a 2.0.36 kernel with M-System provided
> drivers and it worked fine.


I had the exact same problem but I am running an Ampro P5e with DOC 2000
(2.4.1 kernel).

I knew it had a valid NFTL boot record, because it would boot to DOS,
and running the nftldump util under linux would find it. It had been
NFTL formatted with M-Systems utils.

I fixed it by formatting with nftl_format (also comes with MTD source),
providing it a 240k offset so it would not trash the BIOS at the
beginning of the chip (Ampro specific).

Works fine! So, what's the difference between the two formats?!?
Both start at the exact same place on the DOC, as seen by running
nftldump before and after.

Saul.

       reply	other threads:[~2001-08-01  3:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E15RXGo-00058Q-00@pentafluge.infradead.org>
2001-08-01  3:46 ` Saul Thurrowgood [this message]
2001-08-07  9:36   ` DOC 2000 driver (NFTL) in kernel 2.4.7 David Woodhouse
2001-08-08  4:30     ` Alexandru Harsanyi
2001-08-08  6:42       ` David Woodhouse
2001-08-08  7:42         ` Alexandru Harsanyi
2001-08-08  8:52           ` David Woodhouse
2001-07-31  4:40 Alexandru Harsanyi
2001-07-31 20:45 ` 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=3B677B90.B2E244BD@cvs.anu.edu.au \
    --to=saul@cvs.anu.edu.au \
    --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