From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bootchart: Submit a patch questions ...
Date: Thu, 24 Mar 2016 22:15:09 +0100 [thread overview]
Message-ID: <20160324221509.28f24024@free-electrons.com> (raw)
In-Reply-To: <003001d185dd$c7fa6ec0$57ef4c40$@novadsp.com>
Hello,
On Thu, 24 Mar 2016 14:59:35 -0000, g4 at novadsp.com wrote:
> I've been using bootchart just to experiment with getting stuff into the
> buildroot framework. Is there any interest in a patch to add bootchart as an
> option?
Yes, if it was useful for you, it might certainly be useful to others.
Though it is worth mentioning that Busybox includes a minimal version
of bootchartd, so maybe the full bootchart is not useful for everybody.
But that doesn't mean we shouldn't have a package for the full featured
bootchart.
> 1. For a new package is a single patchfile acceptable?
Yes, if the package is simple.
> 2. Does the makefile need to spell out licensing? (This seems to vary within
> BR)?
Yes, it should. The packages that don't describe the license
information are older packages that have not yet been updated to
include the license information.
> 3. Does the patch need to include the changes to package/config.in? I am
> guessing yes .
Yes.
> 4. Finally locally BR is configured to get its kernel sources and .config
> from a local clone of /linux on github. In such a case can BR actually
> correctly check the dependencies for bootchart? Presumably it does test
> kernel config settings against the local .config stashed in build?
I am not sure to fully understand the question, but if I understand
correctly, you're saying that bootchart requires some specific kernel
configuration options. If that's what you mean, then there are two
cases:
* If the kernel option is needed for bootchart to actually *build*,
then you should modify linux/linux.mk to make sure the relevant
kernel configurations are enabled when bootchart is enabled.
* If the kernel option is only needed for bootchart to work at
runtime, then we generally just recommend to indicate which kernel
options are needed in the help text of bootchart's Config.in file.
Hope this helps,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-24 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:59 [Buildroot] Bootchart: Submit a patch questions g4 at novadsp.com
2016-03-24 21:15 ` Thomas Petazzoni [this message]
2016-03-25 10:53 ` g4 at novadsp.com
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=20160324221509.28f24024@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