From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: Holger Brunck <holger.brunck@keymile.com>
Cc: Stefan Roese <sr@denx.de>,
linux-mtd@lists.infradead.org, "agust@denx.de" <agust@denx.de>,
Detlev Zundel <dzu@denx.de>
Subject: Re: MTD concat support for linux and UBI
Date: Thu, 20 Jan 2011 15:59:51 +0100 [thread overview]
Message-ID: <4D384DE7.10602@aimvalley.nl> (raw)
In-Reply-To: <4D3845AE.2040002@keymile.com>
On 01/20/11 15:24, Holger Brunck wrote:
> Hi all,
> I have got a general question to the MTD concat feature in Linux. Is it allowed
> to concatenate NOR flashes with different writebuffersizes? Currently the code
> allows this.
> If so I see a problem for different sizes when dealing with UBI volumes
> comprehending such flashes. Some days ago some patches were added to adjust the
> min I/O size for UBI to the writebuffersize of the flash. If now two flashes
> with different writebuffersizes are concatenated whats the way forward? I see
> two solutions:
> 1) Using the writebuffersize from the flash with the largest writebuffer for min
> I/O size in UBI.
> 2) Adapting the concat feature in Linux to forbid concatenating flashes with
> different writebuffersizes.
>
You're right.
MTD concat already checks for incompatibilites between the
subdevices and I guess it should take into account writebuffer
size too.
---
N. van Bolhuis.
next prev parent reply other threads:[~2011-01-20 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 14:24 MTD concat support for linux and UBI Holger Brunck
2011-01-20 14:59 ` Norbert van Bolhuis [this message]
2011-01-22 16:07 ` Artem Bityutskiy
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=4D384DE7.10602@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=agust@denx.de \
--cc=dzu@denx.de \
--cc=holger.brunck@keymile.com \
--cc=linux-mtd@lists.infradead.org \
--cc=sr@denx.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.