All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbou@mail.ru>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-mtd@lists.infradead.org, kernel-discuss@handhelds.org
Subject: Re: [PATCH] physmap-concat map platform driver
Date: Fri, 1 Jun 2007 01:58:38 +0400	[thread overview]
Message-ID: <20070531215838.GA1603@zarina> (raw)
In-Reply-To: <20070531212749.GR26191@xi.wantstofly.org>

On Thu, May 31, 2007 at 11:27:49PM +0200, Lennert Buytenhek wrote:
> On Sat, May 26, 2007 at 04:29:25AM +0400, Anton Vorontsov wrote:
> 
> > This is physmap-concat driver, which is plain sa1100-flash.c
> > with factored out arch-specific code. This driver is essential for
> > boards using multiple nonindentical chips on the board.
> 
> Doesn't physmap also support multiple nonidentical chips?

Nope. E.g. if I have two chips, 32M + 16M, second chip will be visible
as 32M, which is wrong. As "workaround" I can register two physmap
devices for each chip. But then I can't concat them, i.e. use two
chips for one partition.

> What physmap doesn't support is multiple discontiguous memory
> regions.

Yes, this is another disadvantage of current physmap.

> Maybe it makes more sense to add that support to physmap
> instead?

Well.. more easier solution would be merging physmap-concat to physmap,
trying make physmap-concat platform_data-compatible.

I can try implement that.

Thanks,

-- 
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.org/bd2

  reply	other threads:[~2007-05-31 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  0:29 [PATCH] physmap-concat map platform driver Anton Vorontsov
2007-05-31 21:27 ` Lennert Buytenhek
2007-05-31 21:58   ` Anton Vorontsov [this message]
2007-06-07 12:07     ` Lennert Buytenhek
2007-06-07 19:04       ` Anton Vorontsov
2008-02-01 13:05     ` Stefan Roese
2008-02-01 14:10       ` Anton Vorontsov

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=20070531215838.GA1603@zarina \
    --to=cbou@mail.ru \
    --cc=buytenh@wantstofly.org \
    --cc=kernel-discuss@handhelds.org \
    --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 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.