From: Artem Bityutskiy <dedekind@infradead.org>
To: Miles Nordin <carton@Ivy.NET>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 3GB limit? *2* GB limit?!
Date: Thu, 05 Feb 2009 11:26:35 +0200 [thread overview]
Message-ID: <1233825995.17790.5.camel@localhost.localdomain> (raw)
In-Reply-To: <oqab92rqd4.fsf@castrovalva.Ivy.NET>
On Wed, 2009-02-04 at 13:47 -0500, Miles Nordin wrote:
> >>>>> "ab" == Artem Bityutskiy <dedekind@infradead.org> writes:
>
> ab> MTD user-space interface is 32-bit, and is simited by
> ab> 2GiB. You have to upgrade it to use larger devices.
>
> I am using mtd-tools from git, pulled a couple days ago. or thought I
> was. What do you mean by upgrade? Do you mean ``redesign the
> interface and rewrite the tools'' or ``use Linux/amd64'' or ``pull
> something else from git''?
Miles,
please, glance at the include/mtd/mtd-abi.h file. This file defines the
interface between user-space applications and MTD devices. Notice that
the "size" field in the "struct mtd_info_user" data structure is 32-bit.
So the size of the MTD device is limited by 4GiB. Look at other data
structures and notice a similar thing.
Thus, you have to invent a new user-space interface for MTD. Internally,
it is 64-bit already. You do not have to have amd64. You have to code,
unfortunately.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-02-05 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 0:58 3GB limit? *2* GB limit?! Miles Nordin
2009-02-04 7:40 ` Artem Bityutskiy
2009-02-04 15:54 ` Mike Frysinger
2009-02-05 9:17 ` Adrian Hunter
2009-02-04 18:47 ` Miles Nordin
2009-02-05 9:26 ` Artem Bityutskiy [this message]
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=1233825995.17790.5.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=carton@Ivy.NET \
--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.