Re: [kbuild-devel] call for eyes - kbuild 2.5 on alpha
On Sat, Dec 15, 2001 at 12:49:18PM +1100, Keith Owens wrote: On Fri, 14 Dec 2001 17:08:18 -0500, Ghozlane Toumi [EMAIL PROTECTED] wrote: - the most used kernel format in the alpha world is the vmlinux.gz rather than vmlinuz. is vmlinuz an standard for kbuild2.5, or should i keep the old vmlinuz.gz ? I want one standard name for vmlinux compressed with gzip - vmlinuz. Part of the problem with kbuild 2.4 is each arch did their own thing, I am trying to standardize. It helps documentation if nothing else. And does this mean everyone will now have a 'vmlinuxz' file instead of a vmlinux.gz too? I'm not sure how this will help documentation, except for maybe simpilify the 'help' for a target. BTW, I have been tweaking the top level Makefile.in and adding some new embedded targets from David Woodhouse, it now looks like this: # List all standard kernel formats and locations for all architectures. [snip] ifsel(CONFIG_VMLINUZ) KERNELFULLNAME:= vmlinuz endif This reminds me, are we going to have global rules for 'vmlinuz' too? ifsel(CONFIG_ZIMAGE) KERNELFULLNAME:= arch/$(ARCH)/boot/zImage endif What if your 'zImage' target has multiple outputs? Or what if you don't want to have your final image in arch/$(ARCH)/boot/ ? ifsel(CONFIG_VMLINUX_SREC) KERNELFULLNAME:= vmlinux.srec endif Ack, is someone going to include the zsrec (I assume srec == motorola S-record deal..) utility in the kernel too now? And will it be in a 'common' place for all of the arches that could use it? ifsel(CONFIG_VMLINUX_BIN) KERNELFULLNAME:= vmlinux.bin endif And what's the 'vmlinux.bin' file? objcopy -O binary or ? -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] call for eyes - kbuild 2.5 on alpha
On Sat, Dec 15, 2001 at 12:49:18PM +1100, Keith Owens wrote: I want one standard name for vmlinux compressed with gzip - vmlinuz. Part of the problem with kbuild 2.4 is each arch did their own thing, I am trying to standardize. It helps documentation if nothing else. After thinking about this abit more, I think it sounds like kbuild-2.5 is trying to make all of the arches do the same thing, and that will be a bit of a problem. Right now each of the arches has a few commonalities. There's a 'zImage' target, and almost everyone makes some sort of gzip'ed vmlinux. But that's about it. On PPC the 'zImage' target will produce at most 5 distinct zImages at once. We also have 4 different ways of writing out the program that actually sets up and runs Linux, and about a dozen different formats for the kernel. So aside from having one place that asks 'What do you want to build for your kernel' (which on PPC could actually be a set of bool's so we could build a zImage.srec and zImage.elf and zImage.bin (ELF header removed)) and not having to have arch-dependant help texts (maybe), I'm not sure what's gained. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] call for eyes - kbuild 2.5 on alpha
On Fri, Dec 14, 2001 at 05:08:18PM -0500, Ghozlane Toumi wrote: - the most used kernel format in the alpha world is the vmlinux.gz rather than vmlinuz. is vmlinuz an standard for kbuild2.5, or should i keep the old vmlinuz.gz ? Why can't the 'VMLINUZ' target produce a vmlinux.gz on alpha? - Is there a way *not to* change the main Makefile.in when adding targets other than vmlinux/z ( and shouldn't we remove any reference to bzimage/zimage from the main Makefile.in as it is an ix86 only kernel format) ? Supposedly we'll be able to suppress options that aren't needed on an arch.. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
