From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] psplash fixes
Date: Mon, 19 Dec 2011 19:12:10 +0000 [thread overview]
Message-ID: <1482711.caT8mReHxH@helios> (raw)
In-Reply-To: <C0A5EF9A-CDED-41D7-B7D0-2FCB16771898@dominion.thruhere.net>
On Monday 19 December 2011 20:02:02 Koen Kooi wrote:
> In OE-classic we had IMAGE_SPLASH. Btw, I'm not using core-image.bbclase.
Well we could always use IMAGE_SPLASH and bring it in via image.bbclass. It
seems to me like something you should be able to enable or exchange easily for
any image.
> >>> Would update-alternatives be needed at all in
> >>> that case?
> >>
> >> It would if you want to change it after booting :)
> >
> > What's the use case for changing the splash image after booting?
>
> If you splash contains text its nice to be able to exchange it as easily as
> the rest of the system.
So is this for i18n? Or do you have something in the text that's likely to
need changing? Might it be better to provide an alternative channel for
displaying text in psplash for that?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-19 19:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 17:43 [PATCH 0/2] psplash fixes Paul Eggleton
2011-12-19 17:43 ` [PATCH 1/2] psplash: use OpenEmbedded logo Paul Eggleton
2011-12-20 9:55 ` Paul Menzel
2011-12-19 17:43 ` [PATCH 2/2] scripts/contrib: add a script to create a psplash image header Paul Eggleton
2011-12-19 17:50 ` [PATCH 0/2] psplash fixes Koen Kooi
2011-12-19 18:22 ` Paul Eggleton
2011-12-19 18:27 ` Koen Kooi
2011-12-19 18:32 ` Paul Eggleton
2011-12-19 18:48 ` Koen Kooi
2011-12-19 18:57 ` Paul Eggleton
2011-12-19 19:02 ` Koen Kooi
2011-12-19 19:12 ` Paul Eggleton [this message]
2011-12-21 15:16 ` Paul Eggleton
2011-12-20 15:31 ` Philip Balister
2011-12-21 15:15 ` Paul Eggleton
2011-12-23 0:00 ` Philip Balister
2011-12-20 7:33 ` Martin Jansa
2011-12-21 15:40 ` 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=1482711.caT8mReHxH@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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