[U-Boot-Users] vmlinux kernel image(IN ELF BINARY format) for making uImage
Hi,
I have several doubts.
1>> The README of U-boot says for generating uImage we have to get vmlinux image in ELF BINARY FORMAT. How do i know if the vmlinuz image that i have is in ELF BINARY format? 2>> I have a vmlinux image compiled from MontaVista Linux for COnsumer Edition. The size of this image is 28 MB but when i use this image in generating uImage the linux.bin that is genrated is of 1.7MB and after gzipping it and finally making uImage the uImage is of 775Kb. How is this possible? What is exactly happening out here? Is it a right way to pass MontaVista Kernel image to Uimage? Why is there so much of reduction in size?
Please help me clear this concept Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131@student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne
In message 1127323823.5f1b939cS3092131@student.rmit.edu.au you wrote:
How do i know if the vmlinuz image that i have is in ELF BINARY format?
Just don't care. The Linux kernel's makefile will just do the right thing.
I have a vmlinux image compiled from MontaVista Linux for COnsumer Edition. The size of this image is 28 MB but when i use this image in generating uImage the linux.bin that is genrated is of 1.7MB and after gzipping it and finally making uImage the uImage is of 775Kb. How is this possible?
The 28 MB contain a lot of symbol tables and debug information which get stripped off when creating the binary image - 1.7 MB sounds right for this. And the gzip compression code is good enough to squueze this into 775 kB. Everything sounds reasonable.
What is exactly happening out here?
Nothing special.
Is it a right way to pass MontaVista Kernel image to Uimage?
Sounds like it is.
Why is there so much of reduction in size?
Because unnnecessary symbol and debug information gets thrown away.
Best regards,
Wolfgang Denk
participants (2)
-
Swapnil Ashok Narkhede -
Wolfgang Denk