All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Robert Kaiser <rob@sysgo.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Map driver usage
Date: Tue, 18 Dec 2001 16:05:45 +0000	[thread overview]
Message-ID: <7139.1008691545@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112181515390.32030-100000@dagobert.svc.sysgo.de>

rob@sysgo.de said:
>  I have a question regarding the usage od the access primitives (e.g.
> xx_read8(), xx_read16(), xx_copy_from() and so on). In writing a map
> driver, can one assume that the MTD layer never calls these functions
> to cross a flash device's block boundary ?

No. JFFS may do large reads which cross eraseblock boundaries, and the 
flash driver will translate that directly into a large ->copy_from call.

> The reason I'm asking is that I am writing a new map driver for a
> board that has a somwhat strange logical flash layout and I would like
> to hide that by "shuffling" some of the blocks so that they appear at
> different offsets. Transforming the offset parameter in the above
> mentioned functions would be an easy way to do this, but it requires
> that these functions are never asked to cross an erase block boundary.

I wouldn't do it in the map driver. Do it in the partitioning layer - 
that's already mucking around with the offsets anyway.

--
dwmw2

  reply	other threads:[~2001-12-18 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 14:39 Map driver usage Robert Kaiser
2001-12-18 16:05 ` David Woodhouse [this message]
2001-12-18 17:13   ` Robert Kaiser
2001-12-18 17:18     ` David Woodhouse
2001-12-18 17:44       ` Robert Kaiser
     [not found]         ` <20544.1008697534@redhat.com>
2001-12-19 13:16           ` Robert Kaiser
2001-12-19 13:21             ` David Woodhouse
2001-12-19 16:42               ` Two flash chips with a gap between them Vladimir Doukhanine
2001-12-19 16:51                 ` David Woodhouse
2001-12-18 17:34     ` Map driver usage Jörn Engel

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=7139.1008691545@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rob@sysgo.de \
    /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.