public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Bernhard Priewasser <priewasser@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: /dev/mtd* not there with latest MTD
Date: Mon, 24 Oct 2005 15:30:21 +0200	[thread overview]
Message-ID: <435CE1ED.8020301@gmail.com> (raw)
In-Reply-To: <200510140825.12934.hs4233@mail.mn-solutions.de>

> I made some old-fanshiond mknod-style device files there. They have the
> same names as devfs without devfsd had, so my software just runs fine.

/dev/mtdblockX works fine, but /dev/mtdX NOT.

Did you only create mtdblocks or mtds too?
Older MTD creates /dev/mtdX with minor numbers X*2; running flash_erase 
(for example) works fine.
Not so with same kernel, but latest CVS: creating exactly the same 
/dev/mtdX as mtdchar.c would do (e.g. older MTD would do), I cannot 
operate the flash properly. flash_erase results in an CFI error:

 > > flash_erase /dev/mtd4
 > Erase Total 1 Units
 > Performing Flash Erase of length 262144 at offset 0x0
 > H720X: block erase error: (status timeout)
 > MTD Erase failure: Input/output error
 > H720X: Waiting for chip to be ready timed out. Status 300080

Hm...

Regards,
Bernhard

      reply	other threads:[~2005-10-24 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 14:41 /dev/mtd* not there with latest MTD Bernhard Priewasser
2005-10-13 16:13 ` Todd Poynor
2005-10-14 10:38   ` Bernhard Priewasser
2005-10-14  6:25 ` Holger Schurig
2005-10-24 13:30   ` Bernhard Priewasser [this message]

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=435CE1ED.8020301@gmail.com \
    --to=priewasser@gmail.com \
    --cc=hs4233@mail.mn-solutions.de \
    --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