From: Abraham vd Merwe <abraham@2d3d.co.za>
To: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: read/write functions
Date: Mon, 4 Jun 2001 17:58:14 +0200 [thread overview]
Message-ID: <20010604175814.A16342@crystal.2d3d.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Hi!
Do you need to implement all read/write/copy functions in the map driver
even if your chip driver only uses some of those functions?
For example, let's say I only use map->read32() and map->write32(), do I
still need map->read16(), etc in my map driver or can I just leave them
uninitialized (NULL)?
--
Regards
Abraham
My cup hath runneth'd over with love.
__________________________________________________________
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 reply other threads:[~2001-06-04 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 15:58 Abraham vd Merwe [this message]
2001-06-04 16:00 ` read/write functions 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=20010604175814.A16342@crystal.2d3d.co.za \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox