linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Gilles <gilles.ganault@free.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [ubifs] "cannot parse device table file 'device_table.txt'"
Date: Fri, 20 May 2011 13:27:21 +0300	[thread overview]
Message-ID: <1305887241.2630.137.camel@localhost> (raw)
In-Reply-To: <ekect6d8fta52gjlpf5faqo81fskllta5k@4ax.com>

On Fri, 2011-05-20 at 11:56 +0200, Gilles wrote:
> On Fri, 20 May 2011 12:27:17 +0300, Artem Bityutskiy
> <dedekind1@gmail.com> wrote:
> >It seems like that device table line is indeed incorrect, or what do you
> >expect mkfs.ubifs to do?
> 
> I used a sample that comes with uClinux and is considered a reference
> to use. If there's more information about what value to put in that
> column or a valid file that I could use, I'm interested. Thank you.

I do not know the right format for the device table either. In your case
you have: start = 0, increment = 1, count = -;

I do not know what "-" means, but mkfs.ubifs interprets it as "zero" and
then complains that you ask it to create zero devices starting from
number zero with increment 0.

May be this '-' means something and mkfs.ubifs does not properly handle
that?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2011-05-20 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 10:49 [ubifs] "cannot parse device table file 'device_table.txt'" Gilles
2011-05-20  9:27 ` Artem Bityutskiy
2011-05-20  9:56   ` Gilles
2011-05-20 10:27     ` Artem Bityutskiy [this message]
2011-05-20 15:28       ` Gilles
2011-05-29 10:35 ` Gilles

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=1305887241.2630.137.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=gilles.ganault@free.fr \
    --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 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).