From: Artem Bityutskiy <dedekind@infradead.org>
To: Monte Copeland <catboatmonte@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: gluebi char vs block devices
Date: Fri, 03 Oct 2008 12:19:56 +0300 [thread overview]
Message-ID: <1223025596.8051.70.camel@sauron> (raw)
In-Reply-To: <1fc50b580810010750g5e817923of9a43f1caaa807da@mail.gmail.com>
On Wed, 2008-10-01 at 09:50 -0500, Monte Copeland wrote:
> What is expected (correct) behavior when reading content of static UBI volumes?
>
> / # cat /sys/class/ubi/ubi0_6/name
> kernel_0
> / # cat /sys/class/ubi/ubi0_6/data_bytes
> 3149958
> / # cat /dev/mtd/kernel_0 | wc -c
> 3149958
> / # cat /dev/mtdblock/kernel_0 | wc -c
> 3149824
>
> On my older UBI platform, the byte count from the
> mtdblock dev is truncated down to an even multiple
> of 512.
Monte,
I am not sure if you satisfied with my answer. But you may
glance at 'ubi_create_gluebi()' function and play with what
we assign to mtd->size.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-10-03 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 14:50 gluebi char vs block devices Monte Copeland
2008-10-03 8:00 ` Artem Bityutskiy
2008-10-03 9:19 ` Artem Bityutskiy [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=1223025596.8051.70.camel@sauron \
--to=dedekind@infradead.org \
--cc=catboatmonte@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.