public inbox for linux-mtd@lists.infradead.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 17:18:21 +0000	[thread overview]
Message-ID: <16691.1008695901@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112181738560.2667-100000@dagobert.svc.sysgo.de>

rob@sysgo.de said:
>  OK, so if I implement the copy_from call to break the large transfer
> into smaller ones if necessary, then I should be safe ?

Depending on the flash chips you're using, maybe. Sometimes you need to 
access the chip with the correct address.


>  Yep. Only my problem here is, that I want some physically
> non-contiguous blocks to form a single MTD partition. Is that possible
> with the MTD partition API ? 

The MTD partitioning code is (currently) just a set of wrappers round the 
real MTD functions, which add an offset and call the real chip driver's 
methods. It's fairly simple to do your own such wrapper rather than using 
the ones in mtdpart.c.

--
dwmw2

  reply	other threads:[~2001-12-18 17:07 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
2001-12-18 17:13   ` Robert Kaiser
2001-12-18 17:18     ` David Woodhouse [this message]
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=16691.1008695901@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox