From: Philippe Leduc <ledphilippe@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: how to do a digest on a flashed uImage ? uimage command evolution
Date: Thu, 2 Jul 2015 13:09:11 +0200 [thread overview]
Message-ID: <CABQt-U=+_8gzKB8K9fM=UE5Un-Q-Wn3k4Q_33+kRUzbi5G2hSQ@mail.gmail.com> (raw)
In-Reply-To: <836000AE-9A04-47B7-9BD4-106A3D487558@jcrosoft.com>
Is this a Linux specific behavior? Because I am trying to boot a RTOS
(PikeOS) without success? (Anyway thank you for the info :) )
Best regards,
Philippe LEDUC
ledphilippe@gmail.com
2015-07-02 12:50 GMT+02:00 Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com>:
>
>> On Jul 2, 2015, at 6:47 PM, Philippe Leduc <ledphilippe@gmail.com> wrote:
>>
>> Well, I am using bootm to start my system: how do you boot your system
>> with a mounted uImage?
>>
>
> bootm /mnt/data simply specialy on arm.
>
> Best Regards,
> J.
>
>> Best regards,
>>
>>
>> Philippe LEDUC
>> ledphilippe@gmail.com
>>
>>
>> 2015-07-02 11:30 GMT+02:00 Jean-Christophe PLAGNIOL-VILLARD
>> <plagnioj@jcrosoft.com>:
>>>
>>>> On Jul 2, 2015, at 4:53 PM, Philippe Leduc <ledphilippe@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> First thank you for the details answers :)
>>>>
>>>> Following your explanations/propositions, I think uimagefs is not
>>>> suited to my needs. I think therefore make an evolution of the uImage
>>>> command to be able to retrieve the size of my image and to copy it
>>>> efficiently into the RAM.
>>>>
>>>> I'll try to propose a patch next week for review. But before that,
>>>> what do you think about thes follwing interface:
>>>>
>>>> uimage - extract/verify/copy uImage
>>>>
>>>> Usage: uimage [-vienc] FILE
>>>>
>>>> Options:
>>>> -i show information about image
>>>> -v verify image
>>>> -e OUTFILE extract image to OUTFILE
>>>> -n NO use image number NO in multifile image
>>>> -c OUTFILE Copy the image to OUTFILE
>>>> -s SIZE Return the size of the uimage file into a VARiable.
>>>>
>>>
>>>
>>> I see no point to extract and copy as you you need to mount it
>>>
>>> and then use cp
>>>
>>> Best Regards,
>>> J.
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-07-02 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:53 Philippe Leduc
2015-07-02 9:30 ` Jean-Christophe PLAGNIOL-VILLARD
2015-07-02 10:47 ` Philippe Leduc
2015-07-02 10:50 ` Jean-Christophe PLAGNIOL-VILLARD
2015-07-02 11:09 ` Philippe Leduc [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='CABQt-U=+_8gzKB8K9fM=UE5Un-Q-Wn3k4Q_33+kRUzbi5G2hSQ@mail.gmail.com' \
--to=ledphilippe@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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