From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] openocd: new package for openocd-0.8.0 (host, target)
Date: Wed, 1 Oct 2014 17:12:10 +0200 [thread overview]
Message-ID: <20141001151210.GL16481@pengutronix.de> (raw)
In-Reply-To: <1412173521.13601.47.camel@ws-apr.office.loc>
On Wed, Oct 01, 2014 at 04:25:21PM +0200, Andreas Pretzsch wrote:
> > > +# @$(call install_tree, openocd, 0, 0, -, /usr/share/openocd/)
> >
> > don't add comments like this either remove this or actually install any
> > useful files.
>
> >From your other reply:
> > > + @$(call install_copy, openocd, 0, 0, 0755, -, /usr/bin/openocd)
> > > > +# @$(call install_tree, openocd, 0, 0, -, /usr/share/openocd/)
> > >
> > > Intentionally disabled. 700kB generic extra data on the target makes no
> > > sense. I doubt there won't be one real use case where the makefile is
> > > not pulled into platform local rules and adapted to copy only the 5
> > > relevant files from this tree. So this is more of a reminder where to
> > > look, so I kept is as comment.
> >
> > I missed this when I commented the patch. Are there any files in
> > /usr/share/openocd/ that are required on the target?
>
> Not strictly out from there.
>
> Beside device-specific firmware and examples, it contains some 500
> config files and tcl scripts. Core and SoC specific configs and setups,
> interface (debug adapter) specific configs, RAM and flash layout
> definitions, (eval) board init routines, some helpers, and so on. For
> the myriad targets OpenOCD supports.
>
> In practice on the target, one will use maybe 5 out of them, sometimes
> even merged into one file, and also adapt it to the specific hardware.
> So a mixture of a few selected ones plus maybe some not even in the
> official package.
>
> I see no sensible way for a preselection here, and in 99% of the cases,
> it will be project specific. So no pre-install. But I like to keep the
> comment for those who will adapt it to their needs, to ease things.
>
> What I'll do in v2 is to switch from install_tree to
> install_alternative_tree, missed that one. But still commented out.
Use install_alternative_tree and add an option for it.
Michael
--
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
next prev parent reply other threads:[~2014-10-01 15:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 17:12 Andreas Pretzsch
2014-09-29 17:27 ` Marc Kleine-Budde
2014-09-29 17:50 ` Andreas Pretzsch
2014-10-01 10:15 ` Michael Olbrich
2014-09-29 17:43 ` Andreas Pretzsch
2014-10-01 10:39 ` Michael Olbrich
2014-10-01 10:29 ` Michael Olbrich
2014-10-01 14:25 ` Andreas Pretzsch
2014-10-01 15:12 ` Michael Olbrich [this message]
2014-10-06 23:18 ` [ptxdist] [PATCH v2 1/2] openocd: new package for openocd-0.8.0 Andreas Pretzsch
2014-10-26 17:24 ` Andreas Pretzsch
2014-11-13 16:46 ` Michael Olbrich
2014-11-16 15:30 ` Andreas Pretzsch
2014-11-19 9:05 ` Michael Olbrich
2014-11-29 14:34 ` Andreas Pretzsch
2014-12-04 15:58 ` Michael Olbrich
2014-10-06 23:18 ` [ptxdist] [PATCH v2 2/2] host-openocd: " Andreas Pretzsch
2014-10-26 17:25 ` Andreas Pretzsch
2014-11-13 16:48 ` Michael Olbrich
2014-11-16 15:42 ` Andreas Pretzsch
2014-11-19 10:32 ` Michael Olbrich
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=20141001151210.GL16481@pengutronix.de \
--to=m.olbrich@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