public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: Josh Boyer <jwboyer@gmail.com>
Subject: Re: mtd_info/mtd_info_user>size wrong type
Date: Sun, 8 Apr 2007 10:42:56 +1200	[thread overview]
Message-ID: <200704081042.57089.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <625fc13d0704061826o6abfc33pd4c11173121561d5@mail.gmail.com>

On Saturday 07 April 2007 13:26, Josh Boyer wrote:
> On 4/6/07, Charles Manning <manningc2@actrix.gen.nz> wrote:
> > Folks
> > As people are starting to use larger NAND partitions (4GB+), an
> > inconsistency in the size field has become apparent.
> >
> > This is a unint32_t which is clearly too small for modern NAND arrays.
>
> Yes, known issue.
>
> > The read/write funcions use loff_t which is correct.
> >
> > It would seem that size needs to be increated to loff_t too.
>
> Have you tried doing that?  I seem to recall hearing that it was a bit
> more involved than just changing the size member to be 64 bit.

I have not tried this though someone is aty present. I do know that someone 
has used YAFFS with Linux on a 6G or so partition.However they wanted a 
really fast nand driver and wrote a custom nand driver.

There definitely are some downstream problems too. It is not just a matter of 
changing the type.

eg using do_div() instead of divides and making sure that the right values 
flow through the whole  mtd subsystem fron nand_base..c right through 
mtdpart, mtdcat, the tools etc.

-- Charles

      reply	other threads:[~2007-04-07 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 20:49 mtd_info/mtd_info_user>size wrong type Charles Manning
2007-04-07  1:26 ` Josh Boyer
2007-04-07 22:42   ` Charles Manning [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=200704081042.57089.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=jwboyer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox