From mboxrd@z Thu Jan 1 00:00:00 1970 From: Behan Webster Date: Tue, 17 Jul 2007 17:37:08 -0400 Subject: [U-Boot-Users] In kernel mkimage In-Reply-To: <625fc13d0707171418i5fb6bddbob505c69635eaa823@mail.gmail.com> References: <625fc13d0707161904n66692bc5v7d337fda7ac5c611@mail.gmail.com> <469C8990.2070309@anagramm.de> <469CD1E7.2090609@websterwood.com> <200707171712.55768.sr@denx.de> <469CE064.3010401@websterwood.com> <625fc13d0707171418i5fb6bddbob505c69635eaa823@mail.gmail.com> Message-ID: <469D3684.40008@websterwood.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Josh Boyer wrote: > On 7/17/07, Behan Webster wrote: >> If it is both easy to build mkimage by itself, and can be distributed as >> a package for the various distros, then most of this issue goes away. > > True. The one thing that might pop up is that distros might object to > 'mkimage' being too generic. Though I think the chance of that being > a large issue is small. We should definitely try and make it > standalone in some fashion. This is a good point. By rights it should be uboot-mkimage or something like that. However, stating that the kernel code depends on mkimage being named mkimage is a good argument. -- Behan Webster behanw at websterwood.com