From: Artem Bityutskiy <dedekind1@gmail.com>
To: shuo.liu@freescale.com
Cc: Artem.Bityutskiy@nokia.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
scottwood@freescale.com, akpm@linux-foundation.org,
leoli@freescale.com, dwmw2@infradead.org
Subject: Re: [PATCH 1/2] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Mon, 12 Dec 2011 23:04:25 +0200 [thread overview]
Message-ID: <1323723871.2297.9.camel@koala> (raw)
In-Reply-To: <1323423775-26951-1-git-send-email-shuo.liu@freescale.com>
On Fri, 2011-12-09 at 17:42 +0800, shuo.liu@freescale.com wrote:
> From: Liu Shuo <b35362@freescale.com>
>
> If we use the Nand flash chip whose number of pages in a block is greater
> than 64(for large page), we must treat the low bit of FBAR as being the
> high bit of the page address due to the limitation of FCM, it simply uses
> the low 6-bits (for large page) of the combined block/page address as the
> FPAR component, rather than considering the actual block size.
Pushed this one to l2-mtd-2.6.git, thanks!
Artem.
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: shuo.liu@freescale.com
Cc: Artem.Bityutskiy@nokia.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
scottwood@freescale.com, akpm@linux-foundation.org,
dwmw2@infradead.org
Subject: Re: [PATCH 1/2] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Mon, 12 Dec 2011 23:04:25 +0200 [thread overview]
Message-ID: <1323723871.2297.9.camel@koala> (raw)
In-Reply-To: <1323423775-26951-1-git-send-email-shuo.liu@freescale.com>
On Fri, 2011-12-09 at 17:42 +0800, shuo.liu@freescale.com wrote:
> From: Liu Shuo <b35362@freescale.com>
>
> If we use the Nand flash chip whose number of pages in a block is greater
> than 64(for large page), we must treat the low bit of FBAR as being the
> high bit of the page address due to the limitation of FCM, it simply uses
> the low 6-bits (for large page) of the combined block/page address as the
> FPAR component, rather than considering the actual block size.
Pushed this one to l2-mtd-2.6.git, thanks!
Artem.
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: shuo.liu@freescale.com
Cc: dwmw2@infradead.org, Artem.Bityutskiy@nokia.com,
scottwood@freescale.com, linux-mtd@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, leoli@freescale.com
Subject: Re: [PATCH 1/2] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Mon, 12 Dec 2011 23:04:25 +0200 [thread overview]
Message-ID: <1323723871.2297.9.camel@koala> (raw)
In-Reply-To: <1323423775-26951-1-git-send-email-shuo.liu@freescale.com>
On Fri, 2011-12-09 at 17:42 +0800, shuo.liu@freescale.com wrote:
> From: Liu Shuo <b35362@freescale.com>
>
> If we use the Nand flash chip whose number of pages in a block is greater
> than 64(for large page), we must treat the low bit of FBAR as being the
> high bit of the page address due to the limitation of FCM, it simply uses
> the low 6-bits (for large page) of the combined block/page address as the
> FPAR component, rather than considering the actual block size.
Pushed this one to l2-mtd-2.6.git, thanks!
Artem.
next prev parent reply other threads:[~2011-12-12 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 9:42 [PATCH 1/2] mtd/nand : set Nand flash page address to FBAR and FPAR correctly shuo.liu
2011-12-09 9:42 ` shuo.liu
2011-12-09 9:42 ` shuo.liu
2011-12-09 9:42 ` [PATCH 2/2 v4] mtd/nand : workaround for Freescale FCM to support large-page Nand chip shuo.liu
2011-12-09 9:42 ` shuo.liu
2011-12-09 9:42 ` shuo.liu
2011-12-09 19:24 ` Scott Wood
2011-12-09 19:24 ` Scott Wood
2011-12-09 19:24 ` Scott Wood
2011-12-09 19:23 ` [PATCH 1/2] mtd/nand : set Nand flash page address to FBAR and FPAR correctly Scott Wood
2011-12-09 19:23 ` Scott Wood
2011-12-09 19:23 ` Scott Wood
2011-12-12 21:04 ` Artem Bityutskiy [this message]
2011-12-12 21:04 ` Artem Bityutskiy
2011-12-12 21:04 ` 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=1323723871.2297.9.camel@koala \
--to=dedekind1@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=shuo.liu@freescale.com \
/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.