From: Tom Zanussi <tom.zanussi@intel.com>
To: nitin.a.kamble@intel.com
Cc: paul.eggleton@linux.intel.com, dvhart@linux.intel.com,
Openembedded-core@lists.openembedded.org,
meta-intel@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 0/2] commits for machine setup tool
Date: Mon, 15 Dec 2014 17:04:13 -0600 [thread overview]
Message-ID: <1418684653.25212.39.camel@picadillo> (raw)
In-Reply-To: <cover.1418667266.git.nitin.a.kamble@intel.com>
On Mon, 2014-12-15 at 10:47 -0800, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> This pull request introduces a new feature called machine-setup-tool, which
> can be used by the BSP. With the use of the tool, BSPs for different boards
> which mainly differ in the text configuration for the target board, can be
> consolidated to use a common BSP.
>
> The tool provides ability to configure the target image at runtime. It also
There doesn't seem to be any documentation for this tool that I can see
here. How does a user set things up to configure the target image at
runtime, or does it just happen?
How do you know it's working or not - there doesn't seem to be any
instructions on how to use or test it.
> provides ability to detect the target boards for automatic configuration of
> the image. The tool can handle any text configuration for the target image.
Great, but how? Are there some files or variables that need tweaking?
> All the configuration manipulation needed for the meta-intel BSP boards is
> already supported in the tool.
>
That's great for meta-intel, but this is oe-core, not sure why that's
mentioned here.
> The tool's configuration is BSP specific and need to be specified separately
> in the BSP layer. For example, for the meta-intel layer, the complementary
> commits can be seen here:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=nitin/machinesetuptool
>
> These commits are enabling the meta-intel layer to support 6 boards with 2
> common BSPs.
>
It's good to have working examples, but I don't think that should
replace documentation.
Tom
> Thanks,
> Nitin
>
>
>
> The following changes since commit 8657c2fd57600e0b0eaf2a14692de7453c78e1bb:
>
> serf: readded md5sum (2014-12-11 11:34:57 +0000)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib nitin/machinesetuptool
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=nitin/machinesetuptool
>
> Nitin A Kamble (2):
> alsa-plugins: a new recipe
> machinesetuptool: a new recipe for setup of a machine
>
> .../machinesetuptool/machinesetuptool_git.bb | 55 ++++++++++++++++++++++
> .../recipes-multimedia/alsa/alsa-plugins_1.0.28.bb | 49 +++++++++++++++++++
> 2 files changed, 104 insertions(+)
> create mode 100644 meta/recipes-bsp/machinesetuptool/machinesetuptool_git.bb
> create mode 100644 meta/recipes-multimedia/alsa/alsa-plugins_1.0.28.bb
>
prev parent reply other threads:[~2014-12-15 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 18:47 [PATCH 0/2] commits for machine setup tool nitin.a.kamble
2014-12-15 18:47 ` [PATCH 1/2] alsa-plugins: a new recipe nitin.a.kamble
2014-12-15 18:47 ` [PATCH 2/2] machinesetuptool: a new recipe for setup of a machine nitin.a.kamble
2014-12-15 23:04 ` Tom Zanussi [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=1418684653.25212.39.camel@picadillo \
--to=tom.zanussi@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=dvhart@linux.intel.com \
--cc=meta-intel@yoctoproject.org \
--cc=nitin.a.kamble@intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=saul.wold@intel.com \
/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