Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "George G. Davis" <gdavis@mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD support for Micron SyncFlash (p/n MT28S4M)?
Date: Mon, 7 Apr 2003 20:20:50 +0200	[thread overview]
Message-ID: <20030407182050.GC8178@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <3E91B790.6040608@mvista.com>

On Mon, 7 April 2003 13:38:24 -0400, George G. Davis wrote:
> 
> I've noticed in the list archives that this has been asked recently. But no
> follow-ups there. So, I'm asking again, has anyone worked on MTD support for
> Micron SyncFlash p/n MT28S4M?
> 
> Here's the data sheet URL for reference:
> 
> 	http://download.micron.com/pdf/datasheets/flash/mt28s4m16lc_6.pdf
> 
> I'm not finding any support for this device in current MTD CVS. I'm 
> interested
> in getting this device supported. So if anyone has started working on 
> support
> for this device, I'ld like to help out.

Looks quite weird to me. Looks like it was designed for XIP, but a
search for "cfi" was unsuccessful.

My guess is that even after you finished the coding, noone else would
use it, so you're on your own. Feel free to ask specific questions,
that's about it.

Maybe the best starting point would be the mtdram driver, adjust it to
this device for read-only access and later look at some flash drivers
when adding write, erase, etc. support.

A hardware debugger really helps, if you can get one.

Jörn

-- 
And spam is a useful source of entropy for /dev/random too!
-- Jasmine Strong

      reply	other threads:[~2003-04-07 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 17:38 MTD support for Micron SyncFlash (p/n MT28S4M)? George G. Davis
2003-04-07 18:20 ` Jörn Engel [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=20030407182050.GC8178@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=gdavis@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox