mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Nicolas Pitre <nico@cam.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: How can I prevent MTD to access the end of a flash device ?
Date: Mon, 24 Apr 2006 16:40:30 +0100	[thread overview]
Message-ID: <1145893231.16166.340.camel@shinybook.infradead.org> (raw)
In-Reply-To: <cda58cb80604231157g58088e0dhb93a91c46deda627@mail.gmail.com>

On Sun, 2006-04-23 at 20:57 +0200, Franck Bui-Huu wrote:
> well, mtd_concat_create() functions doesn't use MTD partitions...and
> what's happening if the user needs to use its own partitions based on
> a device resulting of several concatenated flashes? It migth be
> possible to still use your solution and just fix user partitions but
> it really seems easier to fix the MTD size after it the flash has been
> probed.

MTD partitions aren't like block device partitions. You just get a set
of MTD devices which are like a wrapper around the original.

MTD concat is the same. You should be able to partition and concat and
partition and concat on top of each other to your heart's content. If
you so desire.

> Do you think it's possible to change the size of a mtd device rigth
> after probing it ?

Yes, that works too.

-- 
dwmw2


  reply	other threads:[~2006-04-24 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cda58cb80511070248o6d7a18bex@mail.gmail.com>
2005-11-22 14:58 ` Franck
2005-11-22 15:21   ` Josh Boyer
2005-11-22 15:53   ` Nicolas Pitre
2005-11-24  8:32     ` Franck
2005-11-28 16:55       ` Nicolas Pitre
2006-04-23 17:06     ` Franck Bui-Huu
2006-04-23 17:24       ` Nicolas Pitre
2006-04-23 18:57         ` Franck Bui-Huu
2006-04-24 15:40           ` David Woodhouse [this message]
2006-04-24 16:12             ` Franck Bui-Huu

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=1145893231.16166.340.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=vagabon.xyz@gmail.com \
    /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

all inboxes | Powered by JetHome®