All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Amit Kumar Sharma <amitsharma.9@samsung.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	lkml <linux-kernel@vger.kernel.org>,
	apgmoorthy <moorthy.apg@samsung.com>,
	linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.
Date: Fri, 26 Sep 2008 11:19:36 +0300	[thread overview]
Message-ID: <1222417176.5012.17.camel@sauron> (raw)
In-Reply-To: <A09E9029F2344F78959A3E36179C468E@sisodomain.com>


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 (Битюцкий Артём)

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: Amit Kumar Sharma <amitsharma.9@samsung.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	apgmoorthy <moorthy.apg@samsung.com>,
	linux-mtd@lists.infradead.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	lkml <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.
Date: Fri, 26 Sep 2008 11:19:36 +0300	[thread overview]
Message-ID: <1222417176.5012.17.camel@sauron> (raw)
In-Reply-To: <A09E9029F2344F78959A3E36179C468E@sisodomain.com>


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 (Битюцкий Артём)


  reply	other threads:[~2008-09-26  8:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 12:31 [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available AYYANARPONNUSAMY GANGHEYAMOORTHY
2008-09-22  7:11 ` Kyungmin Park
2008-09-22  7:11   ` Kyungmin Park
2008-09-24 12:35   ` apgmoorthy
2008-09-24 12:35     ` apgmoorthy
2008-09-26  0:31     ` Kyungmin Park
2008-09-26  0:31       ` Kyungmin Park
2008-09-26  4:51       ` Artem Bityutskiy
2008-09-26  4:51         ` Artem Bityutskiy
2008-09-26  5:30         ` Kyungmin Park
2008-09-26  5:30           ` Kyungmin Park
2008-09-26  6:26           ` Artem Bityutskiy
2008-09-26  6:26             ` Artem Bityutskiy
2008-09-26  8:01         ` Amit Kumar Sharma
2008-09-26  8:19           ` Artem Bityutskiy [this message]
2008-09-26  8:19             ` Artem Bityutskiy
2008-09-29  9:28             ` apgmoorthy
2008-09-29  9:28               ` apgmoorthy
2008-10-09 22:57               ` Kyungmin Park
2008-10-09 22:57                 ` Kyungmin Park
     [not found]                 ` <1224331498.6770.1362.camel@macbook.infradead.org>
2008-10-20  5:04                   ` apgmoorthy
2008-10-20  5:54                     ` Artem Bityutskiy
2008-10-22  6:43                       ` apgmoorthy
2008-10-24 14:26                         ` Adrian Hunter
2008-11-03 10:32                           ` apgmoorthy
2008-11-05  8:52                             ` Adrian Hunter
2008-11-07 14:26                               ` Rohit
2008-11-10 15:20                                 ` Adrian Hunter
2008-11-11  3:31                                   ` Amit Kumar Sharma
2008-11-11  7:28                                     ` Adrian Hunter
2008-11-12  5:43                                   ` Rohit
2008-10-20 10:53                     ` David Woodhouse
2008-10-21  5:22                   ` apgmoorthy
2008-10-10  6:34               ` David Woodhouse
2008-10-10  6:34                 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2008-10-16  4:16 apgmoorthy
2008-10-16  4:28 ` Kyungmin Park
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=1222417176.5012.17.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=amitsharma.9@samsung.com \
    --cc=dwmw2@infradead.org \
    --cc=kmpark@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --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 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.