All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com, Richard Genoud <richard.genoud@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: ubifs error at boot "bad node type"
Date: Wed, 16 Jul 2014 14:49:15 +0200	[thread overview]
Message-ID: <53C674CB.8060806@nod.at> (raw)
In-Reply-To: <1405513986.5423.19.camel@sauron.fi.intel.com>

Am 16.07.2014 14:33, schrieb Artem Bityutskiy:
>> Well, actually, fastmap is used on this volume when I boot from NAND.
>> (and I must say, It's fast !)
>> Just this time, as I boot from nfsroot, or from a unclean state,
>> fastmap didn't attached UBI.
>> I'll check if it's still operational.
> 
> Just a head-up: check the Kconfig message for this option, it says that
> even the on-flash format for it may change, although I am not quite sure
> if Richard W. still means this.

Correct, fastmap *is* experimental.
But I'm eager to sort issues out.
And the very last thing I'd do is changing the on-flash layout.

Now the bad news, currently nobody pays me to work on UBI/Fastmap.
This means that paid projects go first.

Thanks,
//richard

  reply	other threads:[~2014-07-16 12:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 10:10 ubifs error at boot "bad node type" Richard Genoud
2014-07-09  0:51 ` hujianyang
2014-07-09  7:23   ` Richard Genoud
2014-07-16  8:29 ` Artem Bityutskiy
2014-07-16 12:02   ` Richard Weinberger
2014-07-16 12:26     ` Richard Genoud
2014-07-16 12:32       ` Richard Weinberger
2014-07-16 14:39         ` Richard Genoud
2014-07-16 12:33       ` Artem Bityutskiy
2014-07-16 12:49         ` Richard Weinberger [this message]
2014-07-16 12:06   ` hujianyang
2014-07-16 12:17 ` Artem Bityutskiy

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=53C674CB.8060806@nod.at \
    --to=richard@nod.at \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.genoud@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.