From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from moutng.kundenserver.de ([212.227.17.10])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <biessmann@corscience.de>) id 1RpJkk-0004jC-KU
	for ptxdist@pengutronix.de; Mon, 23 Jan 2012 14:16:07 +0100
Message-ID: <4F1D5D90.7020506@corscience.de>
Date: Mon, 23 Jan 2012 14:16:00 +0100
From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= <biessmann@corscience.de>
MIME-Version: 1.0
References: <1327165141-8606-1-git-send-email-andreas@biessmann.de>
	<1327243762-24190-1-git-send-email-andreas@biessmann.de>
	<4F1D554C.6090608@corscience.de>
	<20120123130755.GA8695@regiomontanus.bwalle.de>
In-Reply-To: <20120123130755.GA8695@regiomontanus.bwalle.de>
Subject: Re: [ptxdist] [PATCH v2] replace umkimage by u-boot sources
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <bernhard@bwalle.de>

Hi Bernhard,

On 23.01.2012 14:07, Bernhard Walle wrote:
> * Andreas Bie=DFmann <biessmann@corscience.de> [2012-01-23 13:40]:
>>
>> shouldn't we build two different packages (u-boot-tool-mkimage,
>> u-boot-tool-env) here?
> =

> I would add that tools as part of the u-boot package.
> =

> Mixing a host tool with target tools don't sound like a good idea.

no, you got me wrong here. We have a host-u-boot-tools package which
have the mkimage build for the host (currently only that tool, but maybe
sometimes mkenvimage too?). Here we have the target package build for
the specified target architecture (yes some want to run mkimage ion the
target ;)

My question here is, should we provide a u-boot-tool-mkimage-<target
arch>.ipkg and u-boot-tool-env-<target arch>.ipkg here rather than a
u-boot-tools-<target arch>.ipkg which includes mkimage/fw_printenv
depending on the configuration.

best regards

Andreas Bie=DFmann

-- =

ptxdist mailing list
ptxdist@pengutronix.de