From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from dude.hi.pengutronix.de ([2001:6f8:1178:2:21e:67ff:fe11:9c5c])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <rsc@pengutronix.de>) id 1TocRR-0001pa-Cl
	for ptxdist@pengutronix.de; Fri, 28 Dec 2012 17:05:49 +0100
Received: from rsc by dude.hi.pengutronix.de with local (Exim 4.80)
	(envelope-from <rsc@pengutronix.de>) id 1TocRR-0000w9-C2
	for ptxdist@pengutronix.de; Fri, 28 Dec 2012 17:05:49 +0100
Date: Fri, 28 Dec 2012 17:05:49 +0100
From: Robert Schwebel <r.schwebel@pengutronix.de>
Message-ID: <20121228160549.GZ3089@pengutronix.de>
References: <em4c52ac29-1a5b-4cba-bc10-0cfb711eec71@plh001-think>
	<20121227150140.559d9fc1@skate>
	<WC20121228100023.490002@rsi-elektrotechnik.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <WC20121228100023.490002@rsi-elektrotechnik.de>
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

On Fri, Dec 28, 2012 at 11:00:23AM +0100, Josef Holzmayr wrote:
> 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 by Makefile
> c) ???
>
> A penny for your thoughts ;)

See rules/sw-ek-lm3s3748.{in,make} and rules/bare_metal.in for a similar
case with cortex-m3. If you put a DFU firmware loader into the M3 and
connect it via USB, you can even load the firmware in-system.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de