From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mo6-p00-ob.rzone.de ([2a01:238:20a:202:5300::1])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <prvs=1709fef7f1=holzmayr@rsi-elektrotechnik.de>)
	id 1ToWjs-0005mb-QR
	for ptxdist@pengutronix.de; Fri, 28 Dec 2012 11:00:29 +0100
Received: from mail.rsi.local (p5494E814.dip.t-dialin.net [84.148.232.20])
	by smtp.strato.de (joses mo10) (RZmta 31.11 DYNA|AUTH)
	with (RC4-MD5 encrypted) ESMTPA id 905890oBS9WGEH
	for <ptxdist@pengutronix.de>; Fri, 28 Dec 2012 11:00:28 +0100 (CET)
Received: from WorldClient by mail.rsi.local (MDaemon PRO v13.0.3)
	with ESMTP id md50000196514.msg
	for <ptxdist@pengutronix.de>; Fri, 28 Dec 2012 11:00:26 +0100
Date: Fri, 28 Dec 2012 11:00:23 +0100
From: "Josef Holzmayr" <holzmayr@rsi-elektrotechnik.de>
MIME-Version: 1.0
Message-ID: <WC20121228100023.490002@rsi-elektrotechnik.de>
In-Reply-To: <20121227150140.559d9fc1@skate>
References: <em4c52ac29-1a5b-4cba-bc10-0cfb711eec71@plh001-think>
	<20121227150140.559d9fc1@skate>
Subject: Re: [ptxdist] Crosscompile a WIFI USB stick firmware with ptxdist
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

From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> So again, unless you need to make modifications to the firmware, I
> would probably recommend to go with a pre-built version.

Yes, I would strongly recommend exactly the same.
On the other hand, I am thinking at the moment about a constellation
where I have a cortex a9 and a cortex m3 in AMP configuration, and the m3
firmware is also "under development" or project specific as you put it, and=
 not some
binary blob. So what might be suggestions here?

So far I've come up with
a) two separate build processes / ptxdist projects
b) make the m3 build configurable through .in file options and then build b=
y Makefile
c) ???

A penny for your thoughts ;)

Joe


-- =

_____________________________________________________________
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Gesch=E4ftsf=FChrer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


-- =

ptxdist mailing list
ptxdist@pengutronix.de