From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 8/9] fs/iso9660: add Grub splashscreen support
Date: Sun, 29 Dec 2013 18:02:25 +0100 [thread overview]
Message-ID: <20131229180225.16fdabc9@skate> (raw)
In-Reply-To: <20131229164518.GB3567@free.fr>
Dear Yann E. MORIN,
On Sun, 29 Dec 2013 17:45:18 +0100, Yann E. MORIN wrote:
> > That's because the documentation is not up-to-date with the Debian
> > patches additions. Those options are really handled, they really have an
> > effect (I tested it). I learned about them while reading:
> >
> > http://www.katspace.org/computers/Grub_Splash/
>
> Hey! Nice ressource! :-)
>
> Maybe we could add a reference to it somewhere in our docs?
True, I'll add it in the help text of the Splash image support.
> > +static struct builtin builtin_foreground =
> > +{
> > + "foreground",
> > + foreground_func,
> > + BUILTIN_CMDLINE | BUILTIN_MENU | BUILTIN_HELP_LIST,
> > + "foreground RRGGBB",
> > + "Sets the foreground color when in graphics mode."
> > + "RR is red, GG is green, and BB blue. Numbers must be in hexadecimal."
> > +};
>
> But then, to be clean, maybe we'd want to also get rid of 'foreground'
> and 'background' when there's no splashscreen. From the link you quoted:
>
> The "foreground" and "background" commands seem to only take effect
> when a splash image is used; otherwise grub uses the "color" command.
>
> Granted, this does not seem to be strictly required, but I think it'be
> better to just remove it, to avoid the user being puzzled that his
> changing foregroud/background has no effect...
>
> Or at least a comment that basically says:
> # {fore,back}ground have no effect without a splashscreen:
> foreground 000000
> background cccccc
Well, since they have not effect when the splashimage is disabled, I
wanted to avoid adding more code in iso9660.mk/grub.mk. But indeed,
adding a comment might be useful.
I'll respin the series with your comments taken into account, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-29 17:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 14:56 [Buildroot] [PATCH 0/9] iso9660/grub improvements Thomas Petazzoni
2013-12-28 14:56 ` [Buildroot] [PATCH 1/9] fs/iso9660: put the Buildroot boot entry first in Grub menu.lst Thomas Petazzoni
2013-12-28 19:33 ` Yann E. MORIN
2013-12-28 14:56 ` [Buildroot] [PATCH 2/9] grub: enclose network driver options in a sub-menu Thomas Petazzoni
2013-12-28 19:35 ` Yann E. MORIN
2013-12-28 14:56 ` [Buildroot] [PATCH 3/9] grub: replace string option for filesystem selection by booleans Thomas Petazzoni
2013-12-28 19:38 ` Yann E. MORIN
2013-12-28 14:56 ` [Buildroot] [PATCH 4/9] fs/iso9660: select ISO9660 support in Grub Thomas Petazzoni
2013-12-28 19:38 ` Yann E. MORIN
2013-12-28 14:56 ` [Buildroot] [PATCH 5/9] linux: enable initrd/initramfs support when cpio rootfs is chosen Thomas Petazzoni
2013-12-28 19:49 ` Yann E. MORIN
2013-12-29 10:13 ` Thomas Petazzoni
2013-12-29 16:34 ` Yann E. MORIN
2013-12-29 17:00 ` Thomas Petazzoni
2013-12-28 14:56 ` [Buildroot] [PATCH 6/9] fs/iso9660: do not use an initrd in iso image when using initramfs Thomas Petazzoni
2013-12-28 14:56 ` [Buildroot] [PATCH 7/9] grub: really disable splash screen support Thomas Petazzoni
2013-12-28 19:50 ` Yann E. MORIN
2013-12-28 14:56 ` [Buildroot] [PATCH 8/9] fs/iso9660: add Grub splashscreen support Thomas Petazzoni
2013-12-28 21:09 ` Yann E. MORIN
2013-12-29 10:24 ` Thomas Petazzoni
2013-12-29 16:45 ` Yann E. MORIN
2013-12-29 17:02 ` Thomas Petazzoni [this message]
2013-12-28 14:56 ` [Buildroot] [PATCH 9/9] grub: align splashscreen handling with iso9660 code Thomas Petazzoni
2013-12-28 21:14 ` Yann E. MORIN
2013-12-29 10:25 ` Thomas Petazzoni
2013-12-29 11:19 ` [Buildroot] [PATCH 0/9] iso9660/grub improvements Thomas Petazzoni
2013-12-29 16:59 ` Yann E. MORIN
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=20131229180225.16fdabc9@skate \
--to=thomas.petazzoni@free-electrons.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