mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kyungmin Park" <kmpark@infradead.org>
To: apgmoorthy <moorthy.apg@samsung.com>,
	"David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org,
	lkml <linux-kernel@vger.kernel.org>,
	dedekind@infradead.org
Subject: Re: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.
Date: Fri, 10 Oct 2008 07:57:51 +0900	[thread overview]
Message-ID: <9c9fda240810091557j529495d5q284a8ab0e0d752dd@mail.gmail.com> (raw)
In-Reply-To: <000b01c92215$ae62d4e0$3dd66c6b@sisodomain.com>

Hi,
I want to merge it if there are no objection.
David, please commit it at MTD tree.
Thank you,Kyungmin Park.
On Mon, Sep 29, 2008 at 6:28 PM, apgmoorthy <moorthy.apg@samsung.com> wrote:>> Hi David,>>   Please do comment on this patch.>>   "Not to expose whole OOB" suggestion by Kyungmin should be fine , but> looking for your suggestion.>> With Regards> Gangheyamoorthy.A.P>> -----Original Message-----> From: Artem Bityutskiy [mailto:dedekind@infradead.org]> Sent: Friday, September 26, 2008 1:50 PM> To: Amit Kumar Sharma> Cc: Kyungmin Park; apgmoorthy; linux-mtd@lists.infradead.org; Kyungmin Park;> lkml; David Woodhouse> Subject: Re: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.>>> On Fri, 2008-09-26 at 13:31 +0530, Amit Kumar Sharma wrote:>> Hi Artem>>>> we have following erro message  if we maintain 64 bytes>> eccpos.>>>> /flash_eraseall -j /dev/mtd4>> ./flash_eraseall: /dev/mtd4: unable to get NAND oobinfo>>>> ./nandwrite -j /dev/mtd2 /jffs2.img>> MEMSETOOBSEL: Inappropriate ioctl for device>>>> but i think as OneNAND has hw ecc controller so Jffs2 will>> not face any problem>> still i think mtd should consider for 128 bytes eccpos for>> 4K page size.>> Well, anyway, in Linux ABI is a holy cow, you cannot change it.> That is a tough rule. Old user-space binaries have to always> works.>> Thus you may do one of:> 1. Invent a new ioctl for 4KiB page NANDs> 2. Add sysfs support> 3. Just do not expose whole OOB as Kyungmin suggested>> But I think assume dwmw2 would need to comment on this and> tell which approach would agree on.>> --> Best regards,> Artem Bityutskiy (Битюцкий Артём)>>ЪТХ╨{.nг+┴╥÷╝┴╜├+%┼кЪ╠Ищ╤\x17╔┼wЪ╨{.nг+┴╥╔┼{╠ЧG╚²ИЪ┼{ay╨\x1dй┤з≥К,j\a╜╒fё╒╥h ▐О│ЙЪ▒ЙГz_Х╝\x03(╜И ▌┼щ╒j"²З\x1a╤^[m╖ЪЪ╬\a╚ЧG╚²ИЪ╒╦?≥╗Х╜з&ёЬ╖~▐А╤iO∙Ф╛z╥ vь^\x14\x04\x1a╤^[m╖ЪЪц\fЪ╤ЛЪ╒╦?√I╔

  reply	other threads:[~2008-10-09 22:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19198934.52871221827459790.JavaMail.weblogic@epml16>
2008-09-22  7:11 ` Kyungmin Park
2008-09-24 12:35   ` apgmoorthy
2008-09-26  0:31     ` Kyungmin Park
2008-09-26  4:51       ` Artem Bityutskiy
2008-09-26  5:30         ` Kyungmin Park
2008-09-26  6:26           ` Artem Bityutskiy
2008-09-26  8:01         ` Amit Kumar Sharma
2008-09-26  8:19           ` Artem Bityutskiy
2008-09-29  9:28             ` apgmoorthy
2008-10-09 22:57               ` Kyungmin Park [this message]
2008-10-10  6:34               ` David Woodhouse
2008-10-16  4:16 apgmoorthy
2008-10-16  4:28 ` Kyungmin Park
2008-10-20  3:01 ` Kyungmin Park

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=9c9fda240810091557j529495d5q284a8ab0e0d752dd@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=moorthy.apg@samsung.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

all inboxes | Powered by JetHome®