Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "George G. Davis" <gdavis@mvista.com>
To: linux-mtd@lists.infradead.org
Subject: MTD support for Micron SyncFlash (p/n MT28S4M)?
Date: Mon, 07 Apr 2003 13:38:24 -0400	[thread overview]
Message-ID: <3E91B790.6040608@mvista.com> (raw)

Greetings,

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.

Also, FWIW, this URL seems broken for me. But more info _may_ be availble here:

	http://www.syncflash.com

TIA!

-- 
Regards,
George

             reply	other threads:[~2003-04-07 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 17:38 George G. Davis [this message]
2003-04-07 18:20 ` MTD support for Micron SyncFlash (p/n MT28S4M)? Jörn Engel

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=3E91B790.6040608@mvista.com \
    --to=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