Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/2] Improve powerpc-utils with librtas
Date: Mon, 1 Jun 2015 14:05:29 +1000	[thread overview]
Message-ID: <20150601040529.GA10144@ocelot.ozlabs.ibm.com> (raw)
In-Reply-To: <cover.1432015191.git.sam.bobroff@au1.ibm.com>

Hi Baruch,

Thanks again for the reviews. I think I've addressed all of the issues. Is
there anything else I need to do?

Sam.

On Tue, May 19, 2015 at 03:59:54PM +1000, Sam Bobroff wrote:
> 
> Many useful functions are missing from powerpc-utils when built by
> buildroot, because they depend on librtas which is not included.
> 
> This set adds the librtas package, a small patch to fix a problem with
> it's make install target, and tweaks the powerpc-utils config
> to include it. This makes the following additional programs available
> from powerpc-utils:
> 
> * uesensor
> * set_poweron_time
> * drmgr
> * lsslot
> * activate_firmware
> * rtas_ibm_get_vpd
> * serv_config
> * rtas_event_decode
> * sys_ident
> 
> 
> Changes v2 -> v3:
> Patch 2/2: powerpc-utils: optionally use librtas
> 
> Group "with" and "without" clauses.
> 
> 
> Changes v1 -> v2:
> Patch 1/2: librtas: new package
> 
> Remove redundant INSTALL_TARGET=yes.
> Add patch description and patch signed-off-by.
> Rename patch with correct prefix (0001-).
> 
> Patch 2/2: powerpc-utils: optionally use librtas
> 
> Make librtas support in powerpc-utils optional due to size concerns.
> 
> 
> Sam Bobroff (2):
>   librtas: new package
>   powerpc-utils: optionally use librtas
> 
>  package/Config.in                                  |    1 +
>  ...0001-librtas-install-librtas.so.1-symlink.patch |   31 ++++++++++++++++++++
>  package/librtas/Config.in                          |    9 ++++++
>  package/librtas/librtas.mk                         |   26 ++++++++++++++++
>  package/powerpc-utils/Config.in                    |   18 ++++++++++++
>  package/powerpc-utils/powerpc-utils.mk             |    8 ++++-
>  6 files changed, 92 insertions(+), 1 deletion(-)
>  create mode 100644 package/librtas/0001-librtas-install-librtas.so.1-symlink.patch
>  create mode 100644 package/librtas/Config.in
>  create mode 100644 package/librtas/librtas.mk
> 
> -- 
> 1.7.10.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2015-06-01  4:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  5:59 [Buildroot] [PATCH v3 0/2] Improve powerpc-utils with librtas Sam Bobroff
2015-05-19  5:59 ` [Buildroot] [PATCH v3 1/2] librtas: new package Sam Bobroff
2015-07-13 15:32   ` Romain Naour
2015-07-13 15:38     ` Romain Naour
2015-07-13 16:37   ` Thomas Petazzoni
2015-05-19  5:59 ` [Buildroot] [PATCH v3 2/2] powerpc-utils: optionally use librtas Sam Bobroff
2015-07-13 15:44   ` Romain Naour
2015-07-13 16:44   ` Thomas Petazzoni
2015-07-20  3:31     ` Sam Bobroff
2015-06-01  4:05 ` Sam Bobroff [this message]
2015-06-01  4:18   ` [Buildroot] [PATCH v3 0/2] Improve powerpc-utils with librtas Baruch Siach

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=20150601040529.GA10144@ocelot.ozlabs.ibm.com \
    --to=sam.bobroff@au1.ibm.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