From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mail.openembedded.org (Postfix) with ESMTP id 007D460232 for ; Tue, 21 Oct 2014 23:28:49 +0000 (UTC) Received: from mail.nefkom.net (unknown [192.168.8.184]) by mail-out.m-online.net (Postfix) with ESMTP id 3jMrcw16tPz3hjMJ; Wed, 22 Oct 2014 01:28:47 +0200 (CEST) X-Auth-Info: +mzvQNhGUDAWGTUSo5vPSPMz63FdBeRQUXvYD465WNM= Received: from chi.localnet (unknown [195.140.253.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-auth.mnet-online.de (Postfix) with ESMTPSA id 3jMrcv1mnKzvdWR; Wed, 22 Oct 2014 01:28:47 +0200 (CEST) From: Marek Vasut To: Koen Kooi Date: Wed, 22 Oct 2014 01:28:44 +0200 User-Agent: KMail/1.13.7 (Linux/3.13-trunk-amd64; KDE/4.13.1; x86_64; ; ) References: <1413746147-7120-1-git-send-email-marex@denx.de> <1413746147-7120-5-git-send-email-marex@denx.de> <84924DE0-BBAC-45C0-B0B3-66A3EB6841CC@dominion.thruhere.net> In-Reply-To: <84924DE0-BBAC-45C0-B0B3-66A3EB6841CC@dominion.thruhere.net> MIME-Version: 1.0 Message-Id: <201410220128.44782.marex@denx.de> Cc: Paul Eggleton , openembedded-core@lists.openembedded.org Subject: Re: [PATCH 4/7] kernel: Pull uImage generation into separate class X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2014 23:29:00 -0000 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Monday, October 20, 2014 at 12:26:04 PM, Koen Kooi wrote: > > Op 19 okt. 2014, om 21:15 heeft Marek Vasut het volgende > > geschreven: > > > > Pull the uImage image format generation from kernel.bbclass into > > a separate kernel-uimage.bbclass. The recipes which now need to > > generate an uImage will have to inherit kernel-uimage instead of > > kernel class. > > To keep backward compatibility, could you rework this into something like: > > kernel.bbclass: > inherit kernel-${KERNEL_IMAGETYPE} > > kernel-${KERNEL_IMAGETYPE}: > inherit kernel-base > imagetype stuff > > kernel-base: > old kernel.bbclass stuff > > That would keep existing BSPs working *and* split out the image types. Yes, this makes sense. Are there any traps inside kernel.bbclass I should be careful about? Like for example ${PN} or other possible variables which are set based on the name of the file? Thanks! Best regards, Marek Vasut