linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Gerhard Sittig <gsi@denx.de>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: nandwrite and contiguous space
Date: Sat, 12 Apr 2014 12:30:22 +0400	[thread overview]
Message-ID: <5348F99E.1070306@list.ru> (raw)
In-Reply-To: <CAFLxGvz_KQBq5zqm1zyQVgM5asW93vgQ9+CjRtDHfsSHv8ST7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

05.04.2014 02:00, Richard Weinberger пишет:
> On Wed, Apr 2, 2014 at 6:19 AM, Stas Sergeev <stsp@list.ru> wrote:
>> 01.04.2014 22:23, Gerhard Sittig пишет:
>>> If you want a sequence of good blocks, this very much sounds like
>>>
>>> the LEBs which UBI provides.  Aren't you asking for an UBI
>>> volume?  What am I missing?
>> Is is possible to configure ubi leb size to be multiple
>> physically contiguous eraseblocks? With some googling
>> it seems not, or what am I missing?
> No, this is not possible.
OK so I patched nandwrite.
The patch is attached only for the preliminary review or
if someone wants to help me with testing this.
The problem is that I don't know how to even test it.
What tool should I use to mark blocks as bad, test
the patch, and then unmark the blocks back to good?

[-- Attachment #2: nandpatch.tar.gz --]
[-- Type: application/gzip, Size: 4735 bytes --]

      reply	other threads:[~2014-04-12  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  9:30 nandwrite and contiguous space Stas Sergeev
2014-04-01 18:23 ` Gerhard Sittig
2014-04-01 19:25   ` Stas Sergeev
2014-04-02  4:19   ` Stas Sergeev
2014-04-04 22:00     ` Richard Weinberger
2014-04-12  8:30       ` Stas Sergeev [this message]

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=5348F99E.1070306@list.ru \
    --to=stsp@list.ru \
    --cc=gsi@denx.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.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 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).