linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: hs@denx.de
Cc: Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: Re: mtd-util, flash_erase: MEMGETOOBSEL on davinci based board fail
Date: Tue, 20 Sep 2011 14:27:49 +0300	[thread overview]
Message-ID: <1316518076.4849.53.camel@sauron> (raw)
In-Reply-To: <4E784790.4010601@denx.de>

On Tue, 2011-09-20 at 09:58 +0200, Heiko Schocher wrote:
> Now the questions:
> 
> a) is this fix Ok? (Has it i chance to go in mainline?)

No, it breaks ABI.

> b) in include/mtd/mtd-abi.h I found this comment:
> 
> /*
>  * Obsolete legacy interface. Keep it in order not to break userspace
>  * interfaces
>  */
> struct nand_oobinfo {
> 
> so this Interface should not be used ... which Interface should be
> used instead?

You are lucky because Brian already took care of this. You need to use
his MEMWRITE ioctl. Try my l2 tree (or take patches from that tree) plus
the "brian" branch of the mtd-utils tree. The idea is that the new ioctl
should get to mainline soon, and we'll merge the brian branch into the
master branch in mtd-utils.

My tree: http://git.infradead.org/users/dedekind/l2-mtd-2.6.git
(you can use it or pick patches from there)
MTD utils tree: http://git.infradead.org/users/dedekind/mtd-utils.git
(use the "brian" branch)

Of course we are interested to know if it worked for you. Brian is in
CC.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2011-09-20 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  7:58 mtd-util, flash_erase: MEMGETOOBSEL on davinci based board fail Heiko Schocher
2011-09-20  8:08 ` Artem Bityutskiy
2011-09-20  8:20   ` Heiko Schocher
2011-09-20 11:27 ` Artem Bityutskiy [this message]
2011-09-20 12:45   ` Artem Bityutskiy
2011-09-20 12:51     ` Heiko Schocher
2011-09-20 13:27     ` Heiko Schocher
2011-09-20 20:48       ` Brian Norris
2011-09-21  6:37         ` Heiko Schocher

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=1316518076.4849.53.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=hs@denx.de \
    --cc=linux-mtd@lists.infradead.org \
    /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).