All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Molton <spyro@f2s.com>
To: linux-mtd@lists.infradead.org
Subject: Re: supporting stupid chips part II
Date: Sat, 21 Aug 2004 00:26:33 +0100	[thread overview]
Message-ID: <20040821002633.13ba0927.spyro@f2s.com> (raw)
In-Reply-To: <20040820132332.42c78dcc.spyro@f2s.com>

Hi.

I've hacked some new read/write functions and a new command function
too, and I can now get to the 24th block before it complains that every
subsequent block is a bad erase block.

The controller is a pest. for writes of commands, it needs bytes. for
the address it needs a word.

for everything else? god only knows. I think probably words for data
transfers.

having never used MTD before, Im not sure how to go about testing it.

Does it require userspace tools?
Should I see anything in /proc/mtd (or anywhere else) ?
What should I expect it to do, given the disk probably has a SSFDC DOS
filesystem on it (winCE handheld device)?

  reply	other threads:[~2004-08-20 23:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 12:23 supporting stupid chips Ian Molton
2004-08-20 23:26 ` Ian Molton [this message]
2004-08-22 13:10   ` supporting stupid chips part III Ian Molton
2004-08-22 23:38     ` supporting stupid chips part IV Ian Molton
2004-08-22 23:43       ` Ian Molton

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=20040821002633.13ba0927.spyro@f2s.com \
    --to=spyro@f2s.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.