From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Thu, 05 Feb 2009 14:23:41 +0100 Subject: [Buildroot] What's up with the kernel names? (Again) In-Reply-To: ("Thiago A. =?utf-8?Q?Corr=C3=AAa=22's?= message of "Thu\, 5 Feb 2009 00\:33\:10 -0200") References: <873aeue676.fsf@macbook.be.48ers.dk> Message-ID: <87vdrpaug2.fsf@macbook.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Thiago" == Thiago A Corr?a writes: Thiago> Hi, >> To me the sane thing would just be for the files to be named whatever >> the kernel names them (uImage/zImage/bzImage/..), but even if we don't >> do that we should atleast make the 2 Linux types use the same style. >> Thiago> Unless someone oposes, I will commit the patch below tomorrow night. Please do it today, I'm planning on cutting the release tomorrow (Friday) at noon. Thiago> It will use the rootfs suffix if one is specified for the kernel, but Thiago> if none is supplied, we get default kernel names. Then you can get Thiago> both rootfs and kernel with your board names, dates, etc. And both Thiago> rootfs and kernel names will always match. Seems good, but don't forget the non-advanced version as well. We should imho use the same naming convention for both kernel builds. -- Bye, Peter Korsgaard