public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: dr john halewood <john@frumious.unidec.co.uk>
To: David Woodhouse <dwmw2@infradead.org>,
	Simon Wood <Simon.Wood@pace.co.uk>
Cc: "'wear-hard@haven.org'" <wear-hard@haven.org>,
	"'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: M-System DOC Millennium with MTD.
Date: Fri, 9 Mar 71685 12:43:01 +0000	[thread overview]
Message-ID: <0011301200580F.00533@frumious.unidec.co.uk> (raw)
In-Reply-To: <28915.975518673@redhat.com>

On Thu, 30 Nov 2000, David Woodhouse wrote:
>Simon.Wood@pace.co.uk said:
>>  3). Tried to 'mount /dev/nftla /floppy' and got error 'mount: /dev/
>> nftla has wrong major or minor number'.
>
>It hasn't found the DiskOnChip. mount(8) ought to give you a better error 
>than that though.

One tiny possibility: I've managed to get something similar when playing with
some spare DoCs I've got lying around (they're 8Mb 2001s salvaged from broken
wince thin clients). On loading them with the MSys firmware image doc2.fff,
which they suggest using with Linux, I get the following, which is similar to
Simon's error (system is 2.2.17+CVS from infradead.org):
Initializing MTD Layer
Giving out device 0 to M-Systems DiskOnChip 1000
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: mtd-patch-2.2.17,v 1.3 2000/11/15 22:56:48 sjhill Exp $
NFTL_notify_add for M-Systems DiskOnChip 1000
NFTL_open
ENODEV: thisNFTL = 0, minor = 23809, ip = c38c7320, fp = c37fbf68

...which isn't really suprising as it's misdetecting the chip for something it
isn't.  Reloading the DoC firmware with the MSys bloatware fixes it however.
(No, I haven't worked out how it misidentifies it yet).
 This sort of thing probably belongs in an FAQ/mini-HOWTO. I've made quite a
lot of notes already(1) which I'll brush up and submit if anyone's interested
or thinks it's worthwhile. 

cheers
john

(1) I'll leave out the bits about how to remove a DoC with a Swiss Army knife,
but the bit about which pins you can bend or break without it mattering too
much might be useful to other hardware thugs like myself ;-)


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-11-30 12:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-29 17:14 M-System DOC Millennium with MTD Simon Wood
2000-11-29 17:24 ` David Woodhouse
2000-11-30 12:01   ` dr john halewood [this message]
2000-11-30 12:04     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-11-30 17:18 Simon Wood
2000-11-30 17:22 ` David Woodhouse
2000-11-30 17:39 ` dr john halewood
2000-11-30 17:41   ` David Woodhouse
2000-12-03 19:01 john halewood
2000-12-03 19:26 ` David Woodhouse
2000-12-03 19:34 ` 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=0011301200580F.00533@frumious.unidec.co.uk \
    --to=john@frumious.unidec.co.uk \
    --cc=Simon.Wood@pace.co.uk \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.org \
    --cc=wear-hard@haven.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