From: iw3gtf@arcor.de
To: t.remmet@phytec.de
Cc: barebox@lists.infradead.org
Subject: Aw: Re: why UBI static volumes are flagged as DEVFS_IS_CHARACTER_DEV
Date: Thu, 6 Oct 2016 11:20:09 +0200 (CEST) [thread overview]
Message-ID: <2074290715.1345124.1475745609454.JavaMail.ngmail@webmail11.arcor-online.net> (raw)
In-Reply-To: <1475741847.3468.20.camel@lws-tremmet.phytec.de>
----- Original Nachricht ----
Von: Teresa Remmet <t.remmet@phytec.de>
An: iw3gtf@arcor.de
Datum: 06.10.2016 10:17
Betreff: Re: why UBI static volumes are flagged as DEVFS_IS_CHARACTER_DEV
> Hello Giorgio,
>
> Am Mittwoch, den 05.10.2016, 15:23 +0200 schrieb iw3gtf@arcor.de:
> > Hi,
> >
> > I noticed that the commit id c087e0804f0290e9886899e8a3cccb07c4ce088b
> flagged static
> > UBI volumes as DEVFS_IS_CHARACTER_DEV.
> >
> > A consequence of this flag is that commands like:
> >
> > # cp /dev/nand0.ubi_volumes.ubi.my_static_vol file
> >
> > will not work because the cp command will see a src file (the static UBI
> volume) with a size
> > of -1 (FILE_SIZE_STREAM) and keep on reading from the volume until a flood
> of
> > "UBI assert failed in ubi_eba_read_leb at 359" asserts comes out of the
> console.
> >
> > I tried to comment out the flag assignment, just to see what happen:
> >
> > int ubi_volume_cdev_add(struct ubi_device *ubi, struct ubi_volume *vol)
> > {
> > ...
> > cdev->size = vol->used_bytes;
> >
> > // if (vol->vol_type == UBI_STATIC_VOLUME)
> > // cdev->flags = DEVFS_IS_CHARACTER_DEV;
> >
> > cdev->dev = &vol->dev;
> > ...
> >
> > and then the cp command worked than as expected.
> >
> > Could someone shortly confirm that the DEVFS_IS_CHARACTER_DEV flag for
> static UBI volumes
> > is really needed (to avoid some other problems that my superficial test
> does not triggers) ?
>
> the size of a static ubi volume device is equal to the image size you
> flashed. When you create a new static ubi volume the size is 0, as it is
> empty.
> We need the chardev flag to be able to update the static ubi volume or
> barebox will complain that there is not enough space.
>
> Regards,
> Teresa
>
Hi,
thanks for the answer, I knew there must be a reason for it.
Nonetheless it is a bit annoying not to be able to simply extract the content
of a static volume.
In my application the static volume contains a barebox bootloader image for an
imx25 cpu, I used to copy it to an mtd partition at the beginning of the nand flash
with the commands: erase /dev/nand0.barebox ; cp /dev/nand0.ubi_volumes... /dev/barebox
This does not work anymore now.
With a newer imx6 cpu I use the command barebox_update -y /dev/nand0.ubi_volumes...,
this works as expected.
Maybe I should write a new barebox_update command variant for the older cpu.
giorgio
Giorgio, iw3gtf@arcor.de
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-10-06 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 13:23 iw3gtf
2016-10-06 8:17 ` Teresa Remmet
2016-10-07 7:27 ` Sascha Hauer
2016-10-10 8:17 ` Teresa Remmet
2016-10-06 9:20 ` iw3gtf [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=2074290715.1345124.1475745609454.JavaMail.ngmail@webmail11.arcor-online.net \
--to=iw3gtf@arcor.de \
--cc=barebox@lists.infradead.org \
--cc=t.remmet@phytec.de \
/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