From: Alexandre Belloni <alexandre.belloni@piout.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/2] Add lpc3250loader to the host tools
Date: Tue, 7 Feb 2012 15:26:58 +0100 [thread overview]
Message-ID: <20120207142657.GA9121@piout.net> (raw)
In-Reply-To: <CAAXf6LV1icxeia44weRDfuoSwkSbmkZRmdNG+wskWOmgGhOGMw@mail.gmail.com>
On Tue, Feb 07, 2012 at 03:24:11PM +0100, Thomas De Schampheleire wrote :
> On Tue, Feb 7, 2012 at 12:01 PM, Alexandre Belloni
> <alexandre.belloni@piout.net> wrote:
> > diff --git a/package/lpc3250loader/Config.in.host b/package/lpc3250loader/Config.in.host
> > new file mode 100644
> > index 0000000..750080b
> > --- /dev/null
> > +++ b/package/lpc3250loader/Config.in.host
> > @@ -0,0 +1,7 @@
> > +config BR2_PACKAGE_HOST_LPC3250LOADER
> > + ? ? ? bool "host lpc3250loader"
> > + ? ? ? help
> > + ? ? ? ? lpc3250loader is a tool to load/burn programs (in particular kickstart
> > + ? ? ? ? and S1L) on an LPC3250 platform.
>
> Does it make sense to have this config depend on an architecture
> specific variable?
> Although it would still be very broad, depending on BR2_ARCH_arm could
> be a possibility...
>
> This way, users of other architectures are not presented with packages
> that are irrelevant for them...
>
Could be, it wasn't the case for sam-ba though...
--
Alexandre Belloni
next prev parent reply other threads:[~2012-02-07 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 11:01 [Buildroot] [PATCHv2 1/2] Add lpc3250loader to the host tools Alexandre Belloni
2012-02-07 11:01 ` [Buildroot] [PATCHv2 2/2] Add lpc3250loader to lpc3250 configs Alexandre Belloni
2012-03-18 14:42 ` Peter Korsgaard
2012-02-07 14:24 ` [Buildroot] [PATCHv2 1/2] Add lpc3250loader to the host tools Thomas De Schampheleire
2012-02-07 14:26 ` Alexandre Belloni [this message]
2012-02-07 14:32 ` Thomas De Schampheleire
2012-02-07 20:03 ` Arnout Vandecappelle
2012-03-18 14:41 ` Peter Korsgaard
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=20120207142657.GA9121@piout.net \
--to=alexandre.belloni@piout.net \
--cc=buildroot@busybox.net \
/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