public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Saul Thurrowgood <saul@cvs.anu.edu.au>
Cc: Alexandru Harsanyi <a.harsanyi@willhart-tech.com>,
	linux-mtd@lists.infradead.org, "Walser,
	Martin" <mwalser@harris.com>
Subject: Re: DOC 2000 driver (NFTL) in kernel 2.4.7
Date: Tue, 07 Aug 2001 10:36:39 +0100	[thread overview]
Message-ID: <30960.997176999@redhat.com> (raw)
In-Reply-To: <3B677B90.B2E244BD@cvs.anu.edu.au>


saul@cvs.anu.edu.au said:
>  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).

That's normally 48KiB for the standard on-device firmware, I think.

> 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. 

Please upgrade to the latest version from CVS (nftlmount.c v1.20). It'll be 
a lot more explicit about its reasons for rejecting any media headers which 
it finds.

--
dwmw2

  reply	other threads:[~2001-08-07  9:31 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 ` DOC 2000 driver (NFTL) in kernel 2.4.7 Saul Thurrowgood
2001-08-07  9:36   ` David Woodhouse [this message]
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=30960.997176999@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=a.harsanyi@willhart-tech.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mwalser@harris.com \
    --cc=saul@cvs.anu.edu.au \
    /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