All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Berube <eberube@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: MTD Driver problem/question with 384MB MD2202-D384.
Date: Mon, 1 Nov 2004 17:15:33 -0500	[thread overview]
Message-ID: <a084b59f04110114152b341fea@mail.gmail.com> (raw)

I saw a message in the archive from June 2003, but there was no
response that I could find.

This is the DiskOnChip I concerned about.  

Its the 384MB - The MD2202-D384.   
Under Linux with a 2.4.27 patched with MTD kernel

Now I have followed the instructions on building a DOC system from
OReilly's Building Embedded Systems book.  And its pretty straight
forward.  Building/patching the kernel (version 2.4.27) with the MTD
drivers.  However it claims that the MTD drivers don't work with DOCs
with firmware version 5.0 or larger.  Now I don't know if this is
still the case.  Now the book advises replacing the firmware with the
Version 4.2 firmware.  However, this fails on the 384 MB DOC.  Now
when I compile the kernel and run it, and it doesn't seem to find the
DOC.

I have to ask is the MD2202-D384 supported by MTD?  Is there a work
around to get this DOC to work with MTD.  Or am I missing something
and this should all be working.


I would like to note, that I actually have tested a MD2202-D32-X
(32MB) DOC (w/ version 4.2 firmware), and it seems to work.  I haven't
extensively tested it, but it is accessible, which is further than I
have gotten on the 384MB Version.


Any help that can be provided will be greatly appreciated.  

Thank you,
Ed

             reply	other threads:[~2004-11-01 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-01 22:15 Ed Berube [this message]
2004-11-02  9:46 ` MTD Driver problem/question with 384MB MD2202-D384 Thomas Gleixner

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=a084b59f04110114152b341fea@mail.gmail.com \
    --to=eberube@gmail.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.