diff options
| author | Miquel Raynal <miquel.raynal@bootlin.com> | 2024-08-26 11:46:25 +0200 |
|---|---|---|
| committer | David Oberhollenzer <david.oberhollenzer@sigma-star.at> | 2024-10-08 08:14:46 +0200 |
| commit | 7bd5cb8ce3c9d5ee58bcae82aa81f078448d45d2 (patch) | |
| tree | caf1cdfeadc56c751c9fc382a6a387205433d6af | |
| parent | 4bcf49043e7c59284c9dfd41c67d10b7b925e840 (diff) | |
mtd-tests: flash_speed: Drop an apparently useless block
I know no device without a multiple of 2 number of pages in each
block. Even though it might be the case, it is clearly not a big deal
and we don't really care about reading the last page, we are doing a
speed benchmark; so as long as the throughput calculation knows how much
data has been read it's fine. Eitherway, I don't think we ever have
fallen in this block because we would read the content of two pages (so
one past the block) and put it in a page-wide buffer, which would
probably lead to an out-of-bound abort.
Just drop the block.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
| -rw-r--r-- | tests/mtd-tests/flash_speed.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/tests/mtd-tests/flash_speed.c b/tests/mtd-tests/flash_speed.c index 3489233..f542a8d 100644 --- a/tests/mtd-tests/flash_speed.c +++ b/tests/mtd-tests/flash_speed.c @@ -265,13 +265,6 @@ static int read_eraseblock_by_2pages(int ebnum) } buf += sz; } - if (pgcnt % 2) { - err = mtd_read(&mtd, fd, ebnum, i * sz, iobuf, pgsize); - if (err) { - fprintf(stderr, "Error reading block %d, page %d!\n", - ebnum, i*2); - } - } return err; } |