From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Crosscompile a WIFI USB stick firmware with ptxdist
Date: Fri, 28 Dec 2012 17:05:49 +0100 [thread overview]
Message-ID: <20121228160549.GZ3089@pengutronix.de> (raw)
In-Reply-To: <WC20121228100023.490002@rsi-elektrotechnik.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
prev parent reply other threads:[~2012-12-28 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 13:12 Dr. Patrick Langfeld
2012-12-27 14:01 ` Thomas Petazzoni
2012-12-28 10:00 ` Josef Holzmayr
2012-12-28 16:05 ` Robert Schwebel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121228160549.GZ3089@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox