lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABYxbz5ZHpH3pk6KxUcHST2nsK0M39AVUkir8gLErzJiBUaO6Q@mail.gmail.com>
Date:	Sat, 16 Mar 2013 16:13:08 +0530
From:	Anil Kumar <anilk4.v@...il.com>
To:	Javier Martinez Canillas <javier@...hile0.org>
Cc:	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	Tony Lindgren <tony@...mide.com>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	Benoit Cousson <b-cousson@...com>,
	linux-arm <linux-arm-kernel@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Getting kernel uImage build issue on omap2+

Hi Javier,

On Sat, Mar 16, 2013 at 2:53 PM, Javier Martinez Canillas
<javier@...hile0.org> wrote:
> On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar <anilk4.v@...il.com> wrote:
>> Hi,
>>
>> I am getting kernel uImage build issue on omap2+ log[1]
>>
>> Taken kernel branch "for_3.10/dts" from
>> https://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>>
>> Taking reference from
>> https://kernel.googlesource.com/pub/scm/linux/kernel/git/tmlind/linux-omap/+/omap-for-v3.9/multiplatform-enable-signed-v2
>>
>> Am I missing some thing ?
>>
>> [1]
>> anil@...l-laptop:~/Anil/omap3/bcousson$  mkimage -A arm -O linux -T
>> kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d
>> zImage-omap2plus uImage-omap2plus
>> mkimage: Can't open zImage-omap2plus: No such file or directory
>> anil@...l-laptop:~/Anil/omap3/bcousson$
>>
>> Thanks,
>> Anil
>>
>
> Hi Anil,
>
> It seems that Tony's email assumed that you generated a bunch of
> zImages for different platforms and then naming them zImage-$platform.
>
> e.g:
>
> $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
> $ make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules
> zImage-omap2plus
> $ cp cp arch/arm/boot/zImage zImage-omap2plus
>
> and then you can use the command in [1]:
>
> $  mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
> 0x80008000 -n "Linux" -d zImage-omap2plus uImage-omap2plus
>
> anyways, the problem is that zImage-omap2plus does not exist and you
> have to use the zImage generated by "make zImage". What I usually do
> is just:
>
> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
> 0x80008000 -n "Linux" -d arch/arm/boot/zImage uImage-omap2plus
>
> and then copy uImage-omap2plus as uImage on either my board MMC/SD or
> Flash memory.

Thanks, It solved the issue
Anil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ