From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: "Purdie, Richard" <richard.purdie@intel.com>
Subject: Re: [denzil branch] Update to the latest version of psplash
Date: Mon, 06 Aug 2012 14:54:40 -0700 [thread overview]
Message-ID: <50203D20.4040907@intel.com> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C28379D@DFLE30.ent.ti.com>
On 08/06/2012 02:43 PM, Cooper Jr., Franklin wrote:
> In the latest version of psplash
> (http://git.yoctoproject.org/cgit/cgit.cgi/psplash/) there are two
> patches that are not in the version of psplash used in the oe-core
> denzil branch. The first patch called Make it easier to customise
> colours
> <http://git.yoctoproject.org/cgit/cgit.cgi/psplash/commit/?id=84764337a584002a92940323d374b0e417c573a6>moves
> some color definitions from being hardcoded into psplash.c and puts it
> in a new header file called psplash-colors.h. The second patch Fix for
> psplash segmentation fault
> <http://git.yoctoproject.org/cgit/cgit.cgi/psplash/commit/?id=de9979aefbc56af59b4d236a4b63dd19dcdcfb53>fixes
> a segment fault issue.
>
> What I would like to do is update the psplash_git.bb recipe to use the
> latest version of psplash that pulls in these two tweaks. The second
> patch has zero impact on existing users of the pslash recipe. If a
> particular layer tweaks the color definitions in psplash by patching the
> psplash.c file then the second patch mentioned above could result in a
> minor tweak having to be made to those layers to address the changes. In
> oe-classic noticed that there is a patch for psplash
> (http://cgit.openembedded.org/openembedded/tree/recipes/psplash/psplash-ti/0001-configurability-for-rev-422.patch)
> that patches psplash in almost the same exact way as the “Make it easier
> to customize colours” patch.
>
> Are there any objections in bumping the version of psplash to
> incorporate the above mentioned patches? I haven’t seen any layer adjust
> the psplash color definitions so I doubt there truly being any impact at
> all.**
Franklin and I discussed this on IRC and I suggested he bring this up on
the mailing list.
I'm inclined to take and backport the segfault patch into the current
version of psplash in denzil (which is a git recipe fixed at e05374a).
Bumping the SRCREV of the recipe and including the color definitions
patch I'm not so sure about - vocal support from the community could tip
the scales, though, so speak up if this would be of value to you.
The segfault patch is being tracked with bug #2903:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2903
Thanks,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-08-06 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 21:43 [denzil branch] Update to the latest version of psplash Cooper Jr., Franklin
2012-08-06 21:54 ` Scott Garman [this message]
2012-08-06 22:05 ` Otavio Salvador
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=50203D20.4040907@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.