From: David Woodhouse <dwmw2@infradead.org>
To: Stuart Menefy <Stuart.Menefy@st.com>
Cc: mtd@infradead.org
Subject: Re: JEDEC support
Date: Tue, 05 Sep 2000 08:38:14 +0100 [thread overview]
Message-ID: <5095.968139494@passion.cygnus.co.uk> (raw)
In-Reply-To: <1000904191526.ZM12687@bristol.st.com>
Stuart.Menefy@st.com said:
> I'm new to MTD, and unfortunately to get it running on my hardware
> I'm going to need the JEDEC support. I see the code has atrophied a
> little, so before I embark on trying to resurrect it, I was just
> wondering if anyone else had done this work? Alternatively any hints
> on how best to do it would be welcome.
It shouldn't be _too_ much out of date. It just needs you to make it take
the 'bank_size' parameter as an argument to the probe function rather than
storing it in the map_info structure.
> Longer term, I also need to support Intel 28F016 (which is not JEDEC
> or CFI compatible). Anybody else implemented support for these?
The (very) old doc1000 driver does it, I think. Can you probe for these
chips?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-09-05 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 18:15 JEDEC support Stuart Menefy
2000-09-05 7:38 ` David Woodhouse [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=5095.968139494@passion.cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=Stuart.Menefy@st.com \
--cc=mtd@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