From: Brian Foster <brian.foster@maxim-ic.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/2] libmtd: add `mtd_dev_present()' library function
Date: Thu, 2 Feb 2012 14:20:17 +0100 [thread overview]
Message-ID: <201202021420.18252.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <1328182404.28171.161.camel@sauron.fi.intel.com>
On Thursday 02 February 2012 12:33:24 Artem Bityutskiy wrote:
> On Fri, 2012-01-27 at 10:30 -0800, Brian Norris wrote:
> > +int mtd_dev_present(libmtd_t desc, int mtd_num) { [ ... ]
>
> This will only work for relatively newer kernels where MTD has sysfs
> support (2.6.30+). Older kernels have no MTD sysfs support and the sysfs
> file you are stat()'ing won't exist, so this function will always return
> an error.
This is a very plausible concern: Our older system
is mostly deployed with 2.6.26(or even older) kernel,
albeit a 2.6.30 option exists. It has multiple MTD
devices, albeit due to the usage/configuration (and
maybe the use of older mtd-utils?) I suspect the bug
has never been observed.
Our latest system uses 2.6.36, and is where the original
UBI-related bug was observed.
cheers!
-blf-
--
Brian Foster
Principal MTS, Software | La Ciotat, France
Maxim Integrated Products | Web: http://www.maxim-ic.com/
next prev parent reply other threads:[~2012-02-02 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 18:30 [PATCH 1/2] libmtd: add `mtd_dev_present()' library function Brian Norris
2012-01-27 18:30 ` [PATCH 2/2] mtdinfo: fix `--all' for non-consecutive device numbers Brian Norris
2012-01-27 18:32 ` Brian Norris
2012-02-02 11:33 ` [PATCH 1/2] libmtd: add `mtd_dev_present()' library function Artem Bityutskiy
2012-02-02 13:20 ` Brian Foster [this message]
2012-02-03 9:17 ` Artem Bityutskiy
2012-02-08 21:28 ` Brian Norris
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=201202021420.18252.brian.foster@maxim-ic.com \
--to=brian.foster@maxim-ic.com \
--cc=computersforpeace@gmail.com \
--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.