From: Marek Vasut <marek.vasut@gmail.com>
To: David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
Kees Trommel <ctrommel@aimvalley.nl>,
linux-mtd@lists.infradead.org
Subject: Re: Add --skip-all-ffs option to mtd-utils nandwrite
Date: Wed, 7 Dec 2016 15:09:49 +0100 [thread overview]
Message-ID: <d4a1082b-d79a-8c90-b17d-5d559e32308a@gmail.com> (raw)
In-Reply-To: <b2a82878-d9f8-f22b-1993-aeae926a0e40@sigma-star.at>
On 12/07/2016 09:21 AM, David Oberhollenzer wrote:
> On 12/07/2016 06:01 AM, Marek Vasut wrote:
>> + if (skipallffs)
>> + {
>> + for (ii = 0; ii < mtd.min_io_size; ii +=
>> sizeof(uint32_t))
>> + {
>> + if (*(uint32_t*)(writebuf + ii) !=
>> 0xffffffff)
>> + break;
>>
>> Is this memcmp()-alike function ?
>>
>> + }
>> + if (ii == mtd.min_io_size)
>> + allffs = 1;
>> + }
>> + if (!allffs) {
> The point of the patch is not to write a page that is filled with 0xFF bytes.
> A feature that is turned off by default and can be activated via a command
> line switch.
That much I figured out
> The code you are trying to replace tries to figure out if an entire block of
> memory is set to 0xFF. The code path should be conditional, as this feature
> is turned off unless explicitly requested.
And to do that, we need to open-code it like above ?
Looks pretty crappy.
>> This could be simply turned to:
>>
>> ret = 0;
>> if (!memcmp(writebuf, writebuf + 1, mtd.min_io_size - 1)) {
>> ret = mtd_write(....);
>> }
> This does something completely different.
It checks whether the buffer if full of the same bytes, yes ?
Add additional conditions as needed (check whether user provided
the arg and whether byte 0 in the buffer is 0xff and you should
be done).
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-12-07 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 16:14 Add --skip-all-ffs option to mtd-utils nandwrite Kees Trommel
2016-12-05 19:13 ` David Oberhollenzer
2016-12-06 8:29 ` Kees Trommel
2016-12-06 13:19 ` David Oberhollenzer
2016-12-07 5:01 ` Marek Vasut
2016-12-07 8:21 ` David Oberhollenzer
2016-12-07 14:09 ` Marek Vasut [this message]
2016-12-07 16:07 ` Boris Brezillon
2016-12-07 16:31 ` Marek Vasut
2016-12-07 16:59 ` Boris Brezillon
2016-12-08 4:14 ` Marek Vasut
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=d4a1082b-d79a-8c90-b17d-5d559e32308a@gmail.com \
--to=marek.vasut@gmail.com \
--cc=ctrommel@aimvalley.nl \
--cc=david.oberhollenzer@sigma-star.at \
--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