From: Artem Bityutskiy <dedekind@infradead.org>
To: Bruce_Leonard@selinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question about ubimkvol vs. mkfs.ubifs
Date: Tue, 08 Apr 2008 08:43:06 +0300 [thread overview]
Message-ID: <1207633386.8040.112.camel@sauron> (raw)
In-Reply-To: <OFC5391750.C1B34EBF-ON88257424.006DD52A-88257424.006E8EFD@selinc.com>
On Mon, 2008-04-07 at 13:07 -0700, Bruce_Leonard@selinc.com wrote:
> >
> > Is it a secret what is your flash and what is its size? If it is NAND
> > I'd recommend you to test it with Adrian's NAND tests:
> > git://infradead.org/~ahunter/nand-tests.git
> >
> Nope, no secret. We're using Samsung K9WAG08U1A NAND parts in 2GiB, 4GiB,
> and 8GiB configurations. At least we're hoping to get the 4 and 8GiB
> configurations working.
If you are thinking about using UBI, it might be not fast enough if you
have slow I/O which is usually the case if there is not NAND controller.
But anyway, I would be very interested to know UBI attach time for your
flash.
> I've run into a problem in the MTD layer with the
> size field. It's a 32-bit field which isn't big enough to store
> 0x100000000 or 0x200000000 which we need for the two larger
> configurations. Just changing it to a 64-bit field introduces problems
> with other code, so we're looking at using more than one NAND controller
> in our FPGA and concatenating the NAND chips at the MTD level.
Well, I guess it should not be too difficult to fix these 64 bit issues.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-04-08 5:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 23:53 Question about ubimkvol vs. mkfs.ubifs Bruce_Leonard
2008-04-07 0:23 ` Hamish Moffatt
2008-04-07 2:42 ` Bruce_Leonard
2008-04-07 7:27 ` Artem Bityutskiy
2008-04-07 7:37 ` Artem Bityutskiy
2008-04-07 20:07 ` Bruce_Leonard
2008-04-08 5:43 ` Artem Bityutskiy [this message]
2008-04-08 16:45 ` Bruce_Leonard
2008-04-08 16:51 ` Artem Bityutskiy
2008-04-08 16:54 ` 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=1207633386.8040.112.camel@sauron \
--to=dedekind@infradead.org \
--cc=Bruce_Leonard@selinc.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