From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Richard Weinberger <richard@nod.at>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ubiblock: Support UBI volume name or volume ID parameter passing
Date: Mon, 14 Apr 2014 13:42:04 +0300 [thread overview]
Message-ID: <1397472124.3287.6.camel@karhu> (raw)
In-Reply-To: <1397141020-6363-1-git-send-email-ezequiel.garcia@free-electrons.com>
On Thu, 2014-04-10 at 11:43 -0300, Ezequiel Garcia wrote:
> +static int ubi_open_volume_by_id(libubi_t desc, const char *node, int vol_id, int mode)
> {
> + char file[256];
> + struct ubi_dev_info dev_info;
> int err, fd;
> - libubi_t libubi;
>
> - err = parse_opt(argc, argv);
> + err = ubi_get_dev_info(desc, node, &dev_info);
> if (err)
> + return errmsg("cannot get information about UBI device \"%s\"", node);
> +
> + sprintf(file, "/dev/ubi%d_%d", dev_info.dev_num, vol_id);
Device node names may ve anything. Please, do not rely on the "/dev/ubi%
d_%d" naming scheme in the tool.
I think device node can be found out by scanning "/dev" and looking at
the device node major/minor numbers. This is more work of course.
However, libubi does exactly the same assumption about UBI volume names
as you do, so if you move this function to libubi, I think it will be
good enough. At least if someone wants to change this in the future,
then it will only require changing the library, but not its users.
> + fd = open(file, mode);
> + if (fd == -1)
> + errmsg("Failed to open '%s' volume device", file);
> + return fd;
> +}
> +
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-04-14 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 14:43 [PATCH] ubiblock: Support UBI volume name or volume ID parameter passing Ezequiel Garcia
2014-04-14 10:42 ` Artem Bityutskiy [this message]
2014-04-14 18:45 ` Ezequiel Garcia
2014-07-21 20:53 ` Ezequiel Garcia
2014-07-28 16:31 ` Artem Bityutskiy
2014-07-30 14:22 ` Ezequiel Garcia
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=1397472124.3287.6.camel@karhu \
--to=dedekind1@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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