From: Randy Dunlap <rdunlap@infradead.org>
To: Max Staudt <mstaudt@suse.de>,
b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org
Cc: tiwai@suse.com, oneukum@suse.com, msrb@suse.com,
sndirsch@suse.com, michal@markovi.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 13/14] bootsplash: Add main documentation
Date: Fri, 27 Oct 2017 09:48:37 -0700 [thread overview]
Message-ID: <f64d701c-ab6c-b1c4-daf6-7ec48bb73bcf@infradead.org> (raw)
In-Reply-To: <a89a2e39-8f51-c87c-6c1e-8bff307a5181@suse.de>
On 10/27/17 04:19, Max Staudt wrote:
> On 10/25/2017 07:43 PM, Randy Dunlap wrote:
>> On 10/25/17 05:46, Max Staudt wrote:
>>> Signed-off-by: Max Staudt <mstaudt@suse.de>
>>> Reviewed-by: Oliver Neukum <oneukum@suse.com>
>>> ---
>>> Documentation/fb/bootsplash.txt | 169 ++++++++++++++++++++++++++++++++++++++++
>>> 1 file changed, 169 insertions(+)
>>> create mode 100644 Documentation/fb/bootsplash.txt
>>>
>>> diff --git a/Documentation/fb/bootsplash.txt b/Documentation/fb/bootsplash.txt
>>> new file mode 100644
>>> index 000000000000..e2b7c956e6c2
>>> --- /dev/null
>>> +++ b/Documentation/fb/bootsplash.txt
>>> @@ -0,0 +1,169 @@
>>> +
>>> +Bootsplash file format
>>> +=======================
>>> +
>>> +A file specified in the kernel configuration as CONFIG_BOOTSPLASH_FILE or
>>> +specified on the command line as bootsplash.filename will be loaded and
>>> +displayed as soon as fbcon is initialized.
>>
>> How do you create or edit such a file? Do you have a program especially for
>> this? Hopefully not just a hex editor...
>
> Very good question.
>
> I definitely already have a primitive tool for this. However I'm unsure where to put it - it's a fairly low-level tool, so should I add it to the kernel tree?
maybe in $kernel/tools/
> How about bootsplash_file.h - I guess I should I move it to include/uapi/linux/ so external tools can use it?
That sounds correct.
thanks.
--
~Randy
next prev parent reply other threads:[~2017-10-27 16:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 12:45 [RFC 00/14] Kernel based bootsplash Max Staudt
2017-10-25 12:45 ` [RFC 01/14] bootsplash: Initial implementation showing black screen Max Staudt
2017-10-25 17:26 ` Randy Dunlap
2017-10-25 12:45 ` [RFC 02/14] bootsplash: Add platform device Max Staudt
2017-10-25 12:45 ` [RFC 03/14] bootsplash: Flush framebuffer after drawing Max Staudt
2017-10-25 12:45 ` [RFC 04/14] bootsplash: Redraw on suspend/hibernate Max Staudt
2017-10-25 12:45 ` [RFC 05/14] bootsplash: Disable splash on oops Max Staudt
2017-10-25 12:45 ` [RFC 06/14] bootsplash: Disable on SysRq SAK Max Staudt
2017-10-25 12:45 ` [RFC 07/14] bootsplash: Add VT keyboard hook Max Staudt
2017-10-25 12:45 ` [RFC 08/14] bootsplash: Add file reading and picture rendering Max Staudt
2017-10-25 17:32 ` Randy Dunlap
2017-10-25 20:27 ` Takashi Iwai
2017-10-27 11:21 ` Max Staudt
2017-10-25 12:45 ` [RFC 09/14] bootsplash: Add corner positioning Max Staudt
2017-10-25 12:45 ` [RFC 10/14] bootsplash: Add animation support Max Staudt
2017-10-25 17:20 ` Randy Dunlap
2017-10-25 17:23 ` Max Staudt
2017-10-25 12:45 ` [RFC 11/14] bootsplash: Redraw fully on console_unblank Max Staudt
2017-10-25 12:46 ` [RFC 12/14] bootsplash: Add sysfs ABI documentation Max Staudt
2017-10-25 12:46 ` [RFC 13/14] bootsplash: Add main documentation Max Staudt
2017-10-25 17:43 ` Randy Dunlap
2017-10-27 11:19 ` Max Staudt
2017-10-27 16:48 ` Randy Dunlap [this message]
2017-10-25 12:46 ` [RFC 14/14] bootsplash: Update MAINTAINERS Max Staudt
2017-11-09 11:56 ` [RFC 00/14] Kernel based bootsplash Pavel Machek
2017-11-09 12:36 ` Oliver Neukum
2017-11-09 18:45 ` Pavel Machek
2017-11-10 16:53 ` Takashi Iwai
2017-11-09 12:42 ` Takashi Iwai
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=f64d701c-ab6c-b1c4-daf6-7ec48bb73bcf@infradead.org \
--to=rdunlap@infradead.org \
--cc=b.zolnierkie@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@markovi.net \
--cc=msrb@suse.com \
--cc=mstaudt@suse.de \
--cc=oneukum@suse.com \
--cc=sndirsch@suse.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).