From: Abraham vd Merwe <abraham@2d3d.co.za>
To: David Woodhouse <dwmw2@infradead.org>
Cc: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: non cfi flash memory
Date: Tue, 19 Jun 2001 15:43:14 +0200 [thread overview]
Message-ID: <20010619154314.A17475@crystal.2d3d.co.za> (raw)
In-Reply-To: <4395.992957074@redhat.com>; from dwmw2@infradead.org on Tue, Jun 19, 2001 at 14:24:34 +0100
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi David!
> No. You don't need to write a whole driver for it. The existing
> cfi_cmdset_0001 code can driver the chips just fine. All you need to do is
> write a _probe_ routine which can pass control to the existing code, just
> like the cfi_probe does.
>
> There's already a hack in the cfi_probe code to find some non-CFI
> AMD-compatible chips and use the cfi_cmdset_0002 back end. You want
> something similar - but _don't_ add further hacks to the cfi_probe code,
> make it an entirely new probe routine like the AMD one should probably
> have been.
I really think those cfi_cmdset_*.c chip driver modules should be renamed to
something else. It's really confusing since they're not only for CFI chips.
--
Regards
Abraham
The study of non-linear physics is like the study of non-elephant biology.
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Antree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-06-19 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 13:04 non cfi flash memory Xavier DEBREUIL
2001-06-19 13:24 ` David Woodhouse
2001-06-19 13:43 ` Abraham vd Merwe [this message]
2001-06-19 13:51 ` David Woodhouse
2001-06-19 17:09 ` Xavier DEBREUIL
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=20010619154314.A17475@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=dwmw2@infradead.org \
--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