From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cc-tool: new package
Date: Mon, 27 Apr 2015 23:10:28 +0200 [thread overview]
Message-ID: <20150427231028.5a0fd7df@free-electrons.com> (raw)
In-Reply-To: <553E9212.4090805@bis.org.pl>
Dear Marcin Bis,
On Mon, 27 Apr 2015 21:46:26 +0200, Marcin Bis wrote:
> cc-tool is used for interacting with Texas Instrument's Debugger and
> Programmer for RF System-on-Chips.
> http://www.ti.com/tool/cc-debugger
>
> The device is used for programming (and debugging) firmware on various
> TI Low Power RF System-on-Chips (based on 8051 microcontrolers).
>
> I am using it for re-flashing such chips from ARM-based embedded devices
> (running Buildroot generated os) - so I put it under "tools for target"
> category.
Ok.
> TI chips do not have sufficient resources to run Linux on them, so
> adding cc-tool as a host tools in Buildroot does not make sense (in my
> opinion) - the tool has no use on Buildroot generated images.
This is not what a host tools is. A host tool runs on your PC, i.e
where you do the Buildroot build. For sure your PC has sufficient
resources to run cc-tool.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-27 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 13:42 [Buildroot] [PATCH] cc-tool: new package Marcin Bis
2015-04-27 15:31 ` Thomas Petazzoni
2015-04-27 19:46 ` Marcin Bis
2015-04-27 19:50 ` [Buildroot] [PATCH v2] " Marcin Bis
2015-04-28 3:28 ` Baruch Siach
2015-04-28 7:44 ` [Buildroot] [PATCH v3] " Marcin Bis
2015-04-28 9:01 ` Baruch Siach
2015-04-28 9:19 ` [Buildroot] [PATCHv4] " Marcin Bis
2015-05-02 19:00 ` Arnout Vandecappelle
2015-04-27 21:10 ` Thomas Petazzoni [this message]
2015-04-28 7:35 ` [Buildroot] [PATCH] " Marcin Bis
2015-04-28 8:02 ` Thomas Petazzoni
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=20150427231028.5a0fd7df@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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