From: David Woodhouse <dwmw2@infradead.org>
To: Abraham vd Merwe <abraham@2d3d.co.za>
Cc: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: mtd->erasesize
Date: Mon, 04 Jun 2001 13:04:01 +0100 [thread overview]
Message-ID: <18826.991656241@redhat.com> (raw)
In-Reply-To: <20010604134136.A2644@crystal.2d3d.co.za>
abraham@2d3d.co.za said:
> I'm busy writing a driver for the 28Fxxxxx 3V Intel Fast Boot Block
> flash devices (for now only a LART driver since I have no other boards
> to play with).
You should be able to use the same actual chip driver as the CFI code -
cfi_cmdset_0001.c. You just need a piece of code to do the Intel-specific
probe and set up the appropriate structure for the chip driver to use, much
like the existing code for AMD/JEDEC probes which has been merged into
cfi_probe.c, except that it should actually be a separate probe function (as
should the AMD/JEDEC one).
> The problem is that these chips have 8 4k blocks in the beginning and
> the rest is 32k blocks, so effectively there is two erasesize's.
> For now, I'm just skipping the first 8 4k blocks so you can't access
> that with the MTD driver, but I believe this is a design flaw with the
> MTD drivers. It should be able to handle multiple erasesize's for each
> device.
The driver for AMD chips (cfi_cmdset_0002.c) already supports this.
Nobody's yet put similar support into the Intel driver. Feel free to do so
:)
--
dwmw2
next prev parent reply other threads:[~2001-06-04 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 11:41 mtd->erasesize Abraham vd Merwe
2001-06-04 12:04 ` David Woodhouse [this message]
2001-06-04 14:00 ` AW: mtd->erasesize Florian Schirmer / TayTron
2001-06-04 14:22 ` mtd->erasesize Nicolas Pitre
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=18826.991656241@redhat.com \
--to=dwmw2@infradead.org \
--cc=abraham@2d3d.co.za \
--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.