From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: Ashish Pareek <ashish.pareek@drishyasystems.com>
Cc: linux-mtd Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: MTD Limitations
Date: Tue, 30 Dec 2008 10:18:53 +0200 [thread overview]
Message-ID: <4959D96D.3010105@nokia.com> (raw)
In-Reply-To: <3A55DF4F429D4A54BD827D81546E0FE3@drishyanb2>
Ashish Pareek wrote:
> Hi Adrian,
> Currently we are using DM355 based Custom board , that will be having
> another 4k page Nand from Micron (MT29F64G08TAAWP)in parallel with
> exisitng 2k pg Nand (MT29F16G08FAAWC) . we have 4 diff chip select (2
> per chip )determined by the CS0 along with 2 address lines using a
> decoding logic .
>
> I dont think any support for 4k pg NF is available . How could be the
> design possible ?
You will have to make the changes to support 4k pg NF yourself. I do not
have such a device, so I do not know exactly what the requirements are.
>
> Ashish
> ----- Original Message ----- From: "Adrian Hunter"
> <ext-adrian.hunter@nokia.com>
> To: "Ashish Pareek" <ashish.pareek@drishyasystems.com>
> Cc: "linux-mtd Mailing List" <linux-mtd@lists.infradead.org>
> Sent: Monday, December 29, 2008 1:27 PM
> Subject: Re: MTD Limitations
>
>
>> Ashish Pareek wrote:
>>> Does MTD has Limitations to support Nand Flash <=4GB ? Has this issue
>>> is fixed in latest MTD GIT ?
>>
>> The latest MTD GIT does support 4GB NAND flash, however you will
>> need to check your particular driver does not have limitations.
>>
>> Please be aware that the ioctls used by mtd-utils are limited to
>> 32-bit sizes. That means they do *not* support 4GiB, but they are
>> probably OK for less than 4GiB i.e. 4GiB minus one eraseblock size.
>>
>
prev parent reply other threads:[~2008-12-30 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B7FB0517CFA8454BAB8C36E3A1ABABF2@drishyanb2>
2008-12-29 7:57 ` MTD Limitations Adrian Hunter
[not found] ` <3A55DF4F429D4A54BD827D81546E0FE3@drishyanb2>
2008-12-30 8:18 ` Adrian Hunter [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=4959D96D.3010105@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=ashish.pareek@drishyasystems.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