PATCH: Use uImage make target for linux-omap1

PATCH: Use uImage make target for linux-omap1

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

Hello,

Current uImage generated for omap1 target did not boot on my target.
We are using manual method to create uImage.
This patch uses uImage KERNEL_IMAGETYPE for omap1 targets. I have
tested this on omap5912osk and the resulting uImage booted just fine.

If it is OK please consider this patch for applying.

Thanks

-Khem

[-- Attachment #2: diff --]
[-- Type: application/octet-stream, Size: 1411 bytes --]

#
# old_revision [7954d4275dc1865e011407126cfd455d897e754d]
#
# patch "packages/linux/linux-omap1.inc"
#  from [8fc1c4685852446244d91a93910ed587bdc52aa8]
#    to [c80e56a3ff3b65aedcb557db63f37678a33abfdc]
#
============================================================
--- packages/linux/linux-omap1.inc	8fc1c4685852446244d91a93910ed587bdc52aa8
+++ packages/linux/linux-omap1.inc	c80e56a3ff3b65aedcb557db63f37678a33abfdc
@@ -7,8 +7,7 @@ inherit kernel
 
 inherit kernel
 
-KERNEL_IMAGETYPE = "vmlinux"
-KERNEL_OUTPUT = "${KERNEL_IMAGETYPE}"
+KERNEL_IMAGETYPE = "uImage"
 
 module_autoload_ohci-hcd_omap5912osk = "ohci-hcd"
 
@@ -22,15 +21,9 @@ do_configure_prepend() {
 
         oe_runmake oldconfig
 }
-
 do_deploy() {
-        if [ "${MACHINE}" == "omap5912osk" ]; then
-                install -d ${DEPLOY_DIR_IMAGE}
-                ${OBJCOPY} -O binary -R .note -R .comment -S ${KERNEL_OUTPUT} ${S}/linux.bin
-                gzip -f -9 ${S}/linux.bin
-                mkimage -A arm -O linux -T kernel -C gzip -a 0x10008000 -e 0x10008000 -n "OE" -d ${S}/linux.bin.gz ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${KERNEL_VERSION}-${MACHINE}-${DATETIME}.bin
-                rm ${S}/linux.bin.gz
-        fi
+        install -d ${DEPLOY_DIR_IMAGE}
+        install -m 0644 arch/${ARCH}/boot/${KERNEL_IMAGETYPE} ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${PV}-${MACHINE}-${DATETIME}
 }
 
 do_deploy[dirs] = "${S}"

Re: PATCH: Use uImage make target for linux-omap1

[Luís Vitório Cargnini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

excuse me but I'm using openembedded for my OMAP 5912 and I  dont need
this patch for my device.

Khem Raj wrote:
> Hello,
> 
> Current uImage generated for omap1 target did not boot on my target.
> We are using manual method to create uImage.
> This patch uses uImage KERNEL_IMAGETYPE for omap1 targets. I have
> tested this on omap5912osk and the resulting uImage booted just fine.
> 
> If it is OK please consider this patch for applying.
> 
> Thanks
> 
> -Khem
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

- --
-
------------------------------------------------------------------------------
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 - Building 30
P.O. Box: 90619-900 - Porto Alegre/RS
Phone: +55 51 3320 3500  extension: 7696
-
---------------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGs+NkKNrSZaSIZoURAjopAJ95tKzY55rDneVEMMAzwhusDoJ0kgCgg8P6
x7PE0HgYVeQ1c91g4CSWKjM=
=gRta
-----END PGP SIGNATURE-----

Re: PATCH: Use uImage make target for linux-omap1

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Khem Raj schreef:
> Hello,
> 
> Current uImage generated for omap1 target did not boot on my target.
> We are using manual method to create uImage.
> This patch uses uImage KERNEL_IMAGETYPE for omap1 targets. I have
> tested this on omap5912osk and the resulting uImage booted just fine.
> 
> If it is OK please consider this patch for applying.

I had some troubles with generating uImages earlier in with avr2, efika and at91 kernels.
I added some foo to packages/linux/linux.inc that works for me(TM).

After I figure out why my ubuntu machine doesn't let me login anymore I have some further
updates for it.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGtBpwMkyGM64RGpERAqPqAJ9ZEI13wWti+upRzgEGNkX5xU16SQCgncm7
gS+hEKU8R2AZEQrintj/Iyk=
=mayM
-----END PGP SIGNATURE-----

Re: PATCH: Use uImage make target for linux-omap1

[Philip Balister]

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

I'm running an OSK build atm (with current code). Tomorrow, I want to 
compare how the kernel creates the uImage with the commands in the bbfile.

I tend to agree we should use the kernel build system wherever possible.

I'm concerned that we are having trouble booting various combinations of 
uboot/kernel/file system and would like to have some understanding of 
what is causing the problems. I do not want to fix one persons build at 
the expense of other's.

Of course, the "thesis" is priority number atm, so I will be doind this 
during procrastination time. 
http://www.phdcomics.com/comics/archive.php?comicid=315

Philip

Khem Raj wrote:
> Hello,
> 
> Current uImage generated for omap1 target did not boot on my target.
> We are using manual method to create uImage.
> This patch uses uImage KERNEL_IMAGETYPE for omap1 targets. I have
> tested this on omap5912osk and the resulting uImage booted just fine.
> 
> If it is OK please consider this patch for applying.
> 
> Thanks
> 
> -Khem
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

Re: PATCH: Use uImage make target for linux-omap1

[Khem Raj]

Agreed. I would be happy if anyone else who is using some omap board
try out this patch and check if this works for them or not.

Thanks

-Khem

On 8/4/07, Philip Balister <philip@balister.org> wrote:
> I'm running an OSK build atm (with current code). Tomorrow, I want to
> compare how the kernel creates the uImage with the commands in the bbfile.
>
> I tend to agree we should use the kernel build system wherever possible.
>
> I'm concerned that we are having trouble booting various combinations of
> uboot/kernel/file system and would like to have some understanding of
> what is causing the problems. I do not want to fix one persons build at
> the expense of other's.
>
> Of course, the "thesis" is priority number atm, so I will be doind this
> during procrastination time.
> http://www.phdcomics.com/comics/archive.php?comicid=315
>
>
> Philip
>
> Khem Raj wrote:
> > Hello,
> >
> > Current uImage generated for omap1 target did not boot on my target.
> > We are using manual method to create uImage.
> > This patch uses uImage KERNEL_IMAGETYPE for omap1 targets. I have
> > tested this on omap5912osk and the resulting uImage booted just fine.
> >
> > If it is OK please consider this patch for applying.
> >
> > Thanks
> >
> > -Khem
> >
> >
> > ------------------------------------------------------------------------
>
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
>

Re: PATCH: Use uImage make target for linux-omap1

[Luís Vitório Cargnini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

openembedded is working for my OSK 5912 without this patch I dont felt
it is necessary.

Philip Balister wrote:
> I'm running an OSK build atm (with current code). Tomorrow, I want to
> compare how the kernel creates the uImage with the commands in the bbfile.
> 
> I tend to agree we should use the kernel build system wherever possible.
> 
> I'm concerned that we are having trouble booting various combinations of
> uboot/kernel/file system and would like to have some understanding of
> what is causing the problems. I do not want to fix one persons build at
> the expense of other's.
> 
> Of course, the "thesis" is priority number atm, so I will be doind this
> during procrastination time.
> http://www.phdcomics.com/comics/archive.php?comicid=315
> 
> Philip
> 
> Khem Raj wrote:
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

- --
-
------------------------------------------------------------------------------
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 - Building 30
P.O. Box: 90619-900 - Porto Alegre/RS
Phone: +55 51 3320 3500  extension: 7696
-
---------------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGtPYXKNrSZaSIZoURAkIzAJ0UST47AGlSi2SEdupjXN9sCumYEACdFwos
1RWhnxUs0b+VMC+Z6ML2zTE=
=RszW
-----END PGP SIGNATURE-----

Re: PATCH: Use uImage make target for linux-omap1

[Khem Raj]

On 8/4/07, Luís Vitório Cargnini <lvcargnini@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> openembedded is working for my OSK 5912 without this patch I dont felt
> it is necessary.

I would be happy if you could try this patch and see if it does not
break anything for you.

Re: PATCH: Use uImage make target for linux-omap1

[Philip Balister]

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

I applied the patch locally, rebuilt my kernel, flashed into the OSK and 
  it ran fine. Basically, the patch fixes the kernel name to match the 
image type (previously I called the uImage vmlinux) this causes 
confusion with people who really understand all the kernel names.

Basically, this is one of the earliest contributions to OE and I am glad 
it lasted this long :)

End result, the images should be compatible, and the filename in 
deploy/images changes from vmlinux.... to uImage... The new name 
accurately describes the image.

Philip

Khem Raj wrote:
> On 8/4/07, Luís Vitório Cargnini <lvcargnini@gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> openembedded is working for my OSK 5912 without this patch I dont felt
>> it is necessary.
> 
> I would be happy if you could try this patch and see if it does not
> break anything for you.
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

Re: PATCH: Use uImage make target for linux-omap1

[Khem Raj]

Thanks Philip for trying it out.

On 8/5/07, Philip Balister <philip@balister.org> wrote:
> I applied the patch locally, rebuilt my kernel, flashed into the OSK and
>   it ran fine. Basically, the patch fixes the kernel name to match the
> image type (previously I called the uImage vmlinux) this causes
> confusion with people who really understand all the kernel names.
>
> Basically, this is one of the earliest contributions to OE and I am glad
> it lasted this long :)
>
> End result, the images should be compatible, and the filename in
> deploy/images changes from vmlinux.... to uImage... The new name
> accurately describes the image.
>
> Philip
>
> Khem Raj wrote:
> > On 8/4/07, Luís Vitório Cargnini <lvcargnini@gmail.com> wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> openembedded is working for my OSK 5912 without this patch I dont felt
> >> it is necessary.
> >
> > I would be happy if you could try this patch and see if it does not
> > break anything for you.
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
>