Hi Russell,
I will rephrase the git-description and post v2.
2015-07-21 15:58 GMT+09:00 Masahiro Yamada :
> Hi Russel,
>
> No more comment?
> I answered your question.
>
>
>
>
> 2015-07-11 1:41 GMT+09:00 Masahiro Yamada :
>> Hi Russel,
>>
>>
>> 2015-07-10 19:22 GMT+09:00 Russell King - ARM Li
Hi Russel,
No more comment?
I answered your question.
2015-07-11 1:41 GMT+09:00 Masahiro Yamada :
> Hi Russel,
>
>
> 2015-07-10 19:22 GMT+09:00 Russell King - ARM Linux :
>> On Mon, Jul 06, 2015 at 09:37:04PM +0900, Masahiro Yamada wrote:
>>> [3] Then, re-build "all" and "uImage" simultaneousl
Hi Russel,
2015-07-10 19:22 GMT+09:00 Russell King - ARM Linux :
> On Mon, Jul 06, 2015 at 09:37:04PM +0900, Masahiro Yamada wrote:
>> [3] Then, re-build "all" and "uImage" simultaneously.
>> You will get an invalid uImage at random.
>> $ make -s -j8 ARCH=arm UIMAGE_LOADADDR=0x80208000 all
On Mon, Jul 06, 2015 at 09:37:04PM +0900, Masahiro Yamada wrote:
> [3] Then, re-build "all" and "uImage" simultaneously.
> You will get an invalid uImage at random.
> $ make -s -j8 ARCH=arm UIMAGE_LOADADDR=0x80208000 all uImage
> Image Name: Linux-4.2.0-rc1-8-g1c4c715-d
> Created:
U-Boot is often used to boot the kernel on ARM boards, but uImage
is not built by "make all", so we are often inclined to do
"make all uImage" in a single command, but we should notice a
pitfall behind it. In fact, "make all uImage" could generate an
invalid uImage if it is run with the parallel o
5 matches
Mail list logo
