From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] psplash improvements v2
Date: Thu, 23 Feb 2012 19:30:30 +0000 [thread overview]
Message-ID: <cover.1330025248.git.paul.eggleton@linux.intel.com> (raw)
Implements the psplash changes as discussed on the mailing list [1] and
by the TSC [2].
[1] http://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg13800.html
[2] http://lists.linuxtogo.org/pipermail/tsc/2012-January/000330.html
Since v1 I've done away with the additional script and integrated .png
conversion into the recipe (optional) as well as used alternatives to
allow selecting the psplash at runtime. I also decided against renaming
the default header file as it would break existing bbappends.
Note for meta-yocto there is a corresponding change that should be
applied at the same time which I will send out shortly.
(No changes since the RFC except for rebasing on top of current master.)
The following changes since commit 55f72b98f606c1554eb6edd151292ffdfddf1384:
texi2html: Fix for multilib (2012-02-22 23:01:45 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/oe-psplash
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/oe-psplash
Paul Eggleton (2):
psplash: use OpenEmbedded logo
psplash: allow building multiple splash executables
meta/recipes-core/psplash/files/psplash-poky-img.h | 1959 +++++++++++---------
meta/recipes-core/psplash/psplash_git.bb | 93 +-
2 files changed, 1143 insertions(+), 909 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-02-23 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 19:30 Paul Eggleton [this message]
2012-02-23 19:30 ` [PATCH 1/2] psplash: use OpenEmbedded logo Paul Eggleton
2012-02-23 19:30 ` [PATCH 2/2] psplash: allow building multiple splash executables Paul Eggleton
2012-02-23 20:28 ` [PATCH 0/2] psplash improvements v2 Koen Kooi
2012-02-24 16:45 ` Richard Purdie
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=cover.1330025248.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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