public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: dr john halewood <john@frumious.unidec.co.uk>
To: mtd@infradead.org
Subject: doc2000 geometry problem?
Date: Wed, 11 Oct 71684 18:46:28 +0100	[thread overview]
Message-ID: <00070511345100.24168@frumious.unidec.co.uk> (raw)

I've got a feeling this is going to turn out to be bad hardware but I thought
it would be worth checking first.
  I'm yet another person trying to embed linux using the doc2000 on a
NatSemi-based platform (Geode aka MediaGX - uck). I've got the system up and
running but I've run into a problem (this is with 2.2.16+current mtd cvs). As I
add the modules dmesg looks like this
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.34 2000/06/07 14:48:52 dwmw2 Exp $
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip 2000 found at address 0xD4000
1 flash chips found. Total DiskOnChip size: 8 Mb
Cannot calculate an NFTL geometry to match size of 0x3c0.
Using C:1024 H:0 S:1 (== 0 sects)
nftla: nftla1
 It turns out that /dev/nftla1 is a FAT12 partition: the people who supplied me
with the board also helpfully put their Wince-based thin client software on the
DOC. Now here's the rub: I can't reformat the doc2000. The nftldump, erase and
nftl_format utils all return an error (-1, helpful that) on the
ioctl(blah,MEMGETINFO,&blah) call, which makes me suspect that there's
something about this chip that's not very healthy. Anyone have any clues or
have I just done something really stupid?

cheers
john


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

             reply	other threads:[~2000-07-05 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 10:34 dr john halewood [this message]
2000-07-05 13:11 ` doc2000 geometry problem? David Woodhouse
2000-07-05 13:54   ` dr john halewood

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=00070511345100.24168@frumious.unidec.co.uk \
    --to=john@frumious.unidec.co.uk \
    --cc=mtd@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