From: Per Smitt <per.smitt@sbie.se>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: bad node type after using ubiupdatevol
Date: Tue, 21 Oct 2014 09:59:50 +0000 [thread overview]
Message-ID: <1413885590813.80183@sbie.se> (raw)
In-Reply-To: <1413884755.7906.424.camel@sauron.fi.intel.com>
> > > First of all, do you have fastmap enabled or disabled (check
> > > your .config)
> >
> > It is not at all in my config. I am running a Freescale i.MX28 yocto
> > solution and it uses kernel 2.6.35.3.
>
> Oh, it is so old. There might have been fixes since then. And I am not
> sure how out-of-date the MTD tests are in this kernel.
The kernel is old but the mtd-utils are slightly fresher.
* commit dcea43eba91642939c82739387147da26d572758
| Author: Aaron Sierra <asierra@xes-inc.com>
| Date: Fri Sep 27 11:34:04 2013 -0500
But if I understand you correctly most part of the UBIFS code is in
kernel drivers so it doesn't matter which version of mtd-utils I have.
What would you recommend in this situation. Should I try to compile a
later kernel with my toolchain and see if I can get Linux running with
that one? If so which version of the Linux kernel should I use?
/Per
prev parent reply other threads:[~2014-10-21 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 11:51 bad node type after using ubiupdatevol Per Smitt
2014-10-20 13:30 ` Artem Bityutskiy
[not found] ` <1413813476716.79473@sbie.se>
2014-10-20 14:17 ` SV: " Artem Bityutskiy
[not found] ` <1413882313759.52960@sbie.se>
2014-10-21 9:45 ` Artem Bityutskiy
2014-10-21 9:59 ` Per Smitt [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=1413885590813.80183@sbie.se \
--to=per.smitt@sbie.se \
--cc=dedekind1@gmail.com \
--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 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.