From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cc-tool: new package
Date: Tue, 28 Apr 2015 10:02:36 +0200 [thread overview]
Message-ID: <20150428100236.7ac9ff4e@free-electrons.com> (raw)
In-Reply-To: <553F385A.50308@bis.org.pl>
Dear Marcin Bis,
On Tue, 28 Apr 2015 09:35:54 +0200, Marcin Bis wrote:
> > 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.
>
> As I understand, host-tools are intended for doing something with images
> generated by Buildroot e.g. flashing, generating fs images etc.
Right.
> cc-tool does not fall under this category.
> It is some how similar to openocd, but openocd can be used to debug
> bootloader/Linux kernel running on some SoC-s (so it perfectly makes
> sense here).
Indeed.
> TI chips, which cc-tool talks to - are not able to run Linux at all.
Ok, so what you mean is that those TI chips are typically not connected
to the development PC directly, but are generally connected to the
embedded system that runs Buildroot.
> Of course cc-tool can be added to Buildroot as a host tool too.
> I can prepare the patch if you want.
Nope, if you don't use it, don't do it. I'm fine with a target package
after the explanations you provided.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-28 8:02 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 ` [Buildroot] [PATCH] " Thomas Petazzoni
2015-04-28 7:35 ` Marcin Bis
2015-04-28 8:02 ` Thomas Petazzoni [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=20150428100236.7ac9ff4e@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