All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Bradley <wmb@firmworks.com>
To: linux-mtd@lists.infradead.org
Subject: mtd partitions limited to 4 GB?
Date: Mon, 16 Jun 2008 14:04:06 -1000	[thread overview]
Message-ID: <4856FF76.9000302@firmworks.com> (raw)

In drivers/mtd/mtdpart.c, struct mtd_part has  "u_int32_t offset", thus 
(apparently) limiting the partition start offset to 4 GiB.  Similarly, 
struct mtd_partition in include/linux/mtd/partititions.h has "u_int32_t 
size" and "u_int32_offset".

Now that NAND FLASH device sizes have exceeded that, this appears to be 
a significant limitation.

Is anyone in the mtd community already addressing this?

Fixing the core infrastructure might be as simple as using "loff_t" 
instead of "u_int32_t" for those fields.  However, all of the existing 
partition map parsers appear to have the same 32-bit limitation, so 
partitioning a >4GiB device will require a new or modified partition map 
format.

             reply	other threads:[~2008-06-17  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  0:04 Mitch Bradley [this message]
2008-06-17  0:22 ` mtd partitions limited to 4 GB? Josh Boyer
2008-06-17  0:41 ` Charles Manning
2008-06-18 17:04   ` Bruce_Leonard

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=4856FF76.9000302@firmworks.com \
    --to=wmb@firmworks.com \
    --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.