From: LiuShuo <b35362@freescale.com>
To: <dedekind1@gmail.com>
Cc: Artem.Bityutskiy@nokia.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Tang Yuantian <b29983@freescale.com>,
linux-mtd@lists.infradead.org,
Jerry Huang <Chang-Ming.Huang@freescale.com>,
scottwood@freescale.com, akpm@linux-foundation.org,
leoli@freescale.com, dwmw2@infradead.org
Subject: Re: [PATCH 2/3] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Fri, 18 Nov 2011 10:08:22 +0800 [thread overview]
Message-ID: <4EC5BE16.9080205@freescale.com> (raw)
In-Reply-To: <1321568016.2272.29.camel@koala>
Ok and I want to add another patch before 3/3.
-LiuShuo
> On Tue, 2011-11-15 at 17:29 +0800, b35362@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.
> Looks like this patch depends on the previous white-space clean-up patch
> - could you please refactor it (and 3/3 too) and resend?
Ok and I am going to add another new patch before 3/3.
-LiuShuo
> Artem.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: LiuShuo <b35362@freescale.com>
To: <dedekind1@gmail.com>
Cc: Artem.Bityutskiy@nokia.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Tang Yuantian <b29983@freescale.com>,
linux-mtd@lists.infradead.org,
Jerry Huang <Chang-Ming.Huang@freescale.com>,
scottwood@freescale.com, akpm@linux-foundation.org,
dwmw2@infradead.org
Subject: Re: [PATCH 2/3] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Fri, 18 Nov 2011 10:08:22 +0800 [thread overview]
Message-ID: <4EC5BE16.9080205@freescale.com> (raw)
In-Reply-To: <1321568016.2272.29.camel@koala>
Ok and I want to add another patch before 3/3.
-LiuShuo
> On Tue, 2011-11-15 at 17:29 +0800, b35362@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.
> Looks like this patch depends on the previous white-space clean-up patch
> - could you please refactor it (and 3/3 too) and resend?
Ok and I am going to add another new patch before 3/3.
-LiuShuo
> Artem.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: LiuShuo <b35362@freescale.com>
To: <dedekind1@gmail.com>
Cc: <dwmw2@infradead.org>, <Artem.Bityutskiy@nokia.com>,
<linux-mtd@lists.infradead.org>, <linuxppc-dev@lists.ozlabs.org>,
<akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<leoli@freescale.com>, <scottwood@freescale.com>,
Jerry Huang <Chang-Ming.Huang@freescale.com>,
Tang Yuantian <b29983@freescale.com>
Subject: Re: [PATCH 2/3] mtd/nand : set Nand flash page address to FBAR and FPAR correctly
Date: Fri, 18 Nov 2011 10:08:22 +0800 [thread overview]
Message-ID: <4EC5BE16.9080205@freescale.com> (raw)
In-Reply-To: <1321568016.2272.29.camel@koala>
Ok and I want to add another patch before 3/3.
-LiuShuo
> On Tue, 2011-11-15 at 17:29 +0800, b35362@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.
> Looks like this patch depends on the previous white-space clean-up patch
> - could you please refactor it (and 3/3 too) and resend?
Ok and I am going to add another new patch before 3/3.
-LiuShuo
> Artem.
>
>
next prev parent reply other threads:[~2011-11-18 2:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 9:29 [PATCH 1/3] mtd/nand: fix coding style issue in drivers/mtd/nand/fsl_elbc.c b35362
2011-11-15 9:29 ` b35362
2011-11-15 9:29 ` b35362
2011-11-15 9:29 ` [PATCH 2/3] mtd/nand : set Nand flash page address to FBAR and FPAR correctly b35362
2011-11-15 9:29 ` b35362
2011-11-15 9:29 ` b35362
2011-11-15 9:29 ` [PATCH v3 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip b35362
2011-11-15 9:29 ` b35362
2011-11-15 9:29 ` b35362
2011-11-22 21:04 ` Artem Bityutskiy
2011-11-22 21:04 ` Artem Bityutskiy
2011-11-22 21:04 ` Artem Bityutskiy
2011-11-22 23:55 ` Scott Wood
2011-11-22 23:55 ` Scott Wood
2011-11-22 23:55 ` Scott Wood
2011-11-23 1:56 ` LiuShuo
2011-11-23 1:56 ` LiuShuo
2011-11-23 1:56 ` LiuShuo
2011-11-23 12:14 ` LiuShuo
2011-11-23 12:14 ` LiuShuo
2011-11-23 12:14 ` LiuShuo
2011-11-28 21:41 ` Scott Wood
2011-11-28 21:41 ` Scott Wood
2011-11-28 21:41 ` Scott Wood
2011-11-17 22:13 ` [PATCH 2/3] mtd/nand : set Nand flash page address to FBAR and FPAR correctly Artem Bityutskiy
2011-11-17 22:13 ` Artem Bityutskiy
2011-11-17 22:13 ` Artem Bityutskiy
2011-11-18 2:08 ` LiuShuo [this message]
2011-11-18 2:08 ` LiuShuo
2011-11-18 2:08 ` LiuShuo
2011-11-22 21:05 ` Artem Bityutskiy
2011-11-22 21:05 ` Artem Bityutskiy
2011-11-22 21:05 ` Artem Bityutskiy
2011-11-15 11:26 ` [PATCH 1/3] mtd/nand: fix coding style issue in drivers/mtd/nand/fsl_elbc.c Jenkins, Clive
2011-11-15 11:26 ` Jenkins, Clive
2011-11-15 13:10 ` David Woodhouse
2011-11-15 13:10 ` David Woodhouse
2011-11-15 14:42 ` Jenkins, Clive
2011-11-15 14:42 ` Jenkins, Clive
2011-11-15 14:42 ` Jenkins, Clive
2011-11-15 15:05 ` David Woodhouse
2011-11-15 15:05 ` David Woodhouse
2011-11-15 14:51 ` David Laight
2011-11-15 14:51 ` David Laight
2011-11-15 14:51 ` David Laight
2011-11-17 22:08 ` Artem Bityutskiy
2011-11-17 22:08 ` Artem Bityutskiy
2011-11-17 22:08 ` 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=4EC5BE16.9080205@freescale.com \
--to=b35362@freescale.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=Chang-Ming.Huang@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=b29983@freescale.com \
--cc=dedekind1@gmail.com \
--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 \
/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.