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@xxxxxxxxx 2015-07-02 12:50 GMT+02:00 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx>: > >> On Jul 2, 2015, at 6:47 PM, Philippe Leduc <ledphilippe@xxxxxxxxx> 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@xxxxxxxxx >> >> >> 2015-07-02 11:30 GMT+02:00 Jean-Christophe PLAGNIOL-VILLARD >> <plagnioj@xxxxxxxxxxxx>: >>> >>>> On Jul 2, 2015, at 4:53 PM, Philippe Leduc <ledphilippe@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
