public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: acceptable chip driver limitations
Date: Tue, 5 Jun 2001 10:42:01 +0200	[thread overview]
Message-ID: <20010605104201.A26328@crystal.2d3d.co.za> (raw)

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

Hi!

Is it allright if my chip driver read/write's only accept 32-bit
to/from/len's?

I.e. if I return with -EINVAL if somebody tries to read/write a single byte
or tries to read from a non-dword boundary, is that acceptable or should the
driver cater for word/byte read/writes as well?

If this is the case, it complicates things a lot because for instance in my
case the flash device can only handle 32-bit read/write's and smaller
accesses will have to be emulated.

-- 

Regards
 Abraham

First study the enemy.  Seek weakness.
		-- Romulan Commander, "Balance of Terror", stardate 1709.2

__________________________________________________________
 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 --]

             reply	other threads:[~2001-06-05  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  8:42 Abraham vd Merwe [this message]
     [not found] ` <25630.991730918@redhat.com>
2001-06-05  8:57   ` acceptable chip driver limitations Abraham vd Merwe
2001-06-05  9:00     ` 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=20010605104201.A26328@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