From: Maxim Kammerer <mk@dee.su>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] We should lastrite splashutils in it's current form and not allow it in tree before it's fixed.
Date: Mon, 21 Jul 2014 22:29:29 +0300 [thread overview]
Message-ID: <CAHsXYDDEHQZkR2nityegJb2kdp3tULA8GrJt_EQNUC=wwCiKFA@mail.gmail.com> (raw)
In-Reply-To: <53CD58E4.30304@gentoo.org>
On Mon, Jul 21, 2014 at 9:16 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
> I'm not against dropping splashutils, but is there an alternative to
> creating or managing framebuffer-splash in the tree? fbsplash doesn't
> seem to be there (tho i don't know if that's the same upstream package
> or not)
Fbsplash is a part of splashutils. There is also an fbcondecor kernel
patch, apparently maintained by someone else now. Splashutils have an
extremely complex structure of daemons, control programs, and
interaction with the kernel via UVESAFB — I had to revisit this
structure every time I had to change something wrt. splashutils
integration.
Not to claim that plymouth is the solution — last time I tried it (~ 2
years ago) it was practically unusable with OpenRC. It took control of
the console in some weird and buggy way, etc. I guess you could
integrate it into a specific system with specific video driver, but I
gave up on plymouth as a generic solution. Maybe it works well with
systemd, but from what I gathered the last time, it is (or used to be)
explicitly disabled on unsupported video cards by the relevant
distros.
--
Maxim Kammerer
Liberté Linux: http://dee.su/liberte
next prev parent reply other threads:[~2014-07-21 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 15:52 [gentoo-dev] We should lastrite splashutils in it's current form and not allow it in tree before it's fixed Samuli Suominen
2014-07-21 15:57 ` Samuli Suominen
2014-07-21 18:16 ` Ian Stakenvicius
2014-07-21 19:29 ` Maxim Kammerer [this message]
2014-07-21 20:31 ` Maxim Koltsov
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='CAHsXYDDEHQZkR2nityegJb2kdp3tULA8GrJt_EQNUC=wwCiKFA@mail.gmail.com' \
--to=mk@dee.su \
--cc=gentoo-dev@lists.gentoo.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