From: Ian Molton <spyro@f2s.com>
To: linux-mtd@lists.infradead.org
Subject: supporting stupid chips
Date: Fri, 20 Aug 2004 13:23:32 +0100 [thread overview]
Message-ID: <20040820132332.42c78dcc.spyro@f2s.com> (raw)
Hi.
I've come to the conclusion that my controller only supports word reads from its data register.
the question is, what to do?
My choice would be to provide a read_id function and facility to indicate that read_byte is not available (NULL ptr?). IIRC we can already provide bulk transfer functions anyhow.
If this is OK I can make these changes and submit a patch.
if not, suggestions ?
next reply other threads:[~2004-08-20 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 12:23 Ian Molton [this message]
2004-08-20 23:26 ` supporting stupid chips part II Ian Molton
2004-08-22 13:10 ` supporting stupid chips part III Ian Molton
2004-08-22 23:38 ` supporting stupid chips part IV Ian Molton
2004-08-22 23:43 ` Ian Molton
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=20040820132332.42c78dcc.spyro@f2s.com \
--to=spyro@f2s.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 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.