From: Vitaly Wool <vwool@ru.mvista.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd/utils: sync with MTD ioctl interface rework to get rid of MEMGETOOBSEL/MEMSETOOBSEL
Date: Tue, 06 Dec 2005 13:36:28 +0300 [thread overview]
Message-ID: <439569AC.8080409@ru.mvista.com> (raw)
In-Reply-To: <1133865021.16302.37.camel@tglx.tec.linutronix.de>
Thomas Gleixner wrote:
>On Fri, 2005-12-02 at 10:05 +0300, Vitaly Wool wrote:
>
>
>>Hi,
>>this patch reorganizes the MTD utls to
>>- not use MEMGETOOBSEL/MEMSETOOBSEL ioctls as they're planned for
>>removal and anyway not needed
>>- use MEMGETOOBAVAIL ioctl to get the number of available OOB bytes and
>>read/write OOB accordingly
>>
>>Any input is most welcome.
>>
>>
>
>1. Rendering the utils unusable for older kernels is wrong.
>
>Its simple to handle this in the utils depending on the functionality
>which is exposed by the kernel.
>
>
Makes sense to me.
>
>2. Your current approach prevents me to
>- dump the raw flash content including OOB data
>- write a nand image with given oob data
>
>This is essential for troubleshooting and must still be possible
>somehow.
>
>
>
Lemme disagree with you here. Raw OOB content-related stuff is not IMHO
the thing to debug from userland.
Suggest prinitng out the raw OOB contents for MTD_DEBUG_LEVEL3 instead.
Vitaly
next prev parent reply other threads:[~2005-12-06 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 7:05 [PATCH] mtd/utils: sync with MTD ioctl interface rework to get rid of MEMGETOOBSEL/MEMSETOOBSEL Vitaly Wool
2005-12-02 22:06 ` Todd Poynor
2005-12-05 5:46 ` Vitaly Wool
2005-12-13 0:02 ` Todd Poynor
2005-12-13 0:20 ` Thomas Gleixner
2005-12-06 10:30 ` Thomas Gleixner
2005-12-06 10:36 ` Vitaly Wool [this message]
2005-12-06 10:51 ` Thomas Gleixner
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=439569AC.8080409@ru.mvista.com \
--to=vwool@ru.mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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