From: Vipin Kumar <vipin.kumar@st.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Pratyush ANAND <pratyush.anand@st.com>,
Viresh KUMAR <viresh.kumar@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Deepak SIKRI <deepak.sikri@st.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 28/74] Incrementing the ecc_pos array to contain 128 char
Date: Tue, 31 Aug 2010 12:04:32 +0530 [thread overview]
Message-ID: <4C7CA278.9040902@st.com> (raw)
In-Reply-To: <1283170469.12995.53.camel@brekeke>
On 8/30/2010 5:44 PM, Artem Bityutskiy wrote:
> On Mon, 2010-08-30 at 16:13 +0530, Viresh KUMAR wrote:
>> From: Vipin Kumar <vipin.kumar@st.com>
>>
>> For a page size of 4096, the number of oob bytes are 128 per page. This demands
>> for an increased ecc_pos array as well as ecc can be placed at more than 64
>> locations.
>>
>> This patch is added because SPEAr platforms NAND controller has 13 bytes of ecc
>> for each 512 bytes of data. This results in 104 bytes of ecc in case of 4096
>> byte page.
>>
>> Signed-off-by: Vipin Kumar <vipin.kumar@st.com>
>> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
>
> Nack, breaking ABI Is not allowed in Linux.
>
Hello Artem,
I could not understand your point. Can you please elaborate. How does this patch
break ABI
Regards
Vipin
next prev parent reply other threads:[~2010-08-31 6:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1283161023.git.viresh.kumar@st.com>
2010-08-30 10:43 ` [PATCH 24/74] ST SPEAr: Add smi driver for serial NOR flash Viresh KUMAR
2010-08-30 10:43 ` [PATCH 27/74] ST SPEAr : NAND interface driver for spear platforms Viresh KUMAR
2010-09-01 22:36 ` Linus Walleij
2010-09-02 8:09 ` Armando Visconti
2010-09-02 8:52 ` Armando Visconti
2010-09-02 11:15 ` Linus Walleij
2010-09-02 12:33 ` Armando Visconti
2010-09-03 11:23 ` Alessandro Rubini
2010-09-03 17:26 ` Linus Walleij
2010-09-06 7:25 ` Armando Visconti
2010-09-10 4:21 ` viresh kumar
2010-09-10 8:38 ` Linus Walleij
2010-09-03 7:11 ` Vipin Kumar
2010-09-03 11:22 ` Sebastian RASMUSSEN
2010-08-30 10:43 ` [PATCH 28/74] Incrementing the ecc_pos array to contain 128 char Viresh KUMAR
2010-08-30 12:14 ` Artem Bityutskiy
2010-08-31 6:34 ` Vipin Kumar [this message]
2010-08-31 23:36 ` Artem Bityutskiy
2010-09-01 4:13 ` Vipin Kumar
2010-09-01 10:45 ` Artem Bityutskiy
2010-09-01 11:04 ` Vipin Kumar
2010-09-01 21:23 ` Ryan Mallon
2010-09-01 21:54 ` Kevin Cernekee
2010-09-01 22:21 ` Ryan Mallon
2010-09-01 22:53 ` Artem Bityutskiy
2010-09-01 23:37 ` Ryan Mallon
2010-09-01 23:43 ` Ryan Mallon
2010-09-02 6:33 ` Brian Norris
2010-09-02 9:49 ` Artem Bityutskiy
2010-09-01 23:23 ` Artem Bityutskiy
2010-08-30 10:43 ` [PATCH 29/74] Newly erased page read workaround Viresh KUMAR
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=4C7CA278.9040902@st.com \
--to=vipin.kumar@st.com \
--cc=armando.visconti@st.com \
--cc=bhupesh.sharma@st.com \
--cc=dedekind1@gmail.com \
--cc=deepak.sikri@st.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pratyush.anand@st.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=vipulkumar.samar@st.com \
--cc=viresh.kumar@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).