From: Derek Mulcahy <derek@technicaltoys.net>
To: linux-mtd@lists.infradead.org
Subject: MTD driver for Atmel serial flash
Date: Fri, 26 Oct 2001 08:56:41 -0400 [thread overview]
Message-ID: <3BD95D89.4090701@technicaltoys.net> (raw)
Hi
I am developing an MTD driver for an Atmel serial flash.
The device has 264 byte pages and they can be erased and written
individually.
I'm not sure what values to put in the mtd_info structure. I intend this
to be used with JFFS2.
Currently I have
mtd->name = "atmel";
mtd->type = MTD_OTHER;
mtd->flags = MTD_WRITEB_WRITEABLE | MTD_ERASEABLE | MTD_CLEAR_BITS |
MTD_SET_BITS;
mtd->size = 256 * 2048;
mtd->read = serial_read;
mtd->write = serial_write;
mtd->sync = serial_sync;
mtd->erase = serial_erase;
mtd->erasesize = 256;
As you can see, I am hiding the extra 8 bytes per page from the MTD
system, this makes the read/writes simpler.
An advice/pointers on the right way to do this would be much appreciated.
Cheers
Derek
next reply other threads:[~2001-10-26 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 12:56 Derek Mulcahy [this message]
2001-10-26 13:37 ` MTD driver for Atmel serial flash David Woodhouse
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=3BD95D89.4090701@technicaltoys.net \
--to=derek@technicaltoys.net \
--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