| splash.4 (62978) | splash.4 (65009) |
|---|---|
| 1.\" 2.\" Copyright (c) 1999 3.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26.\" | 1.\" 2.\" Copyright (c) 1999 3.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26.\" |
| 27.\" $FreeBSD: head/share/man/man4/splash.4 62978 2000-07-11 22:39:48Z dannyboy $ | 27.\" $FreeBSD: head/share/man/man4/splash.4 65009 2000-08-23 08:57:59Z sheldonh $ |
| 28.\" 29.Dd February 9, 1999 30.Dt SPLASH 4 31.Os FreeBSD 32.Sh NAME 33.Nm splash 34.Nd 35splash screen / screen saver interface 36.Sh SYNOPSIS 37.Cd "pseudo-device splash" 38.Sh DESCRIPTION 39The 40.Nm 41pseudo device driver adds support for the splash screen and screen 42savers to the kernel. 43This driver is required if the splash bitmap image is to be loaded or 44any screen saver is to be used. 45.Sh SPLASH SCREEN 46You can load and display an arbitrary bitmap image file as a welcome banner | 28.\" 29.Dd February 9, 1999 30.Dt SPLASH 4 31.Os FreeBSD 32.Sh NAME 33.Nm splash 34.Nd 35splash screen / screen saver interface 36.Sh SYNOPSIS 37.Cd "pseudo-device splash" 38.Sh DESCRIPTION 39The 40.Nm 41pseudo device driver adds support for the splash screen and screen 42savers to the kernel. 43This driver is required if the splash bitmap image is to be loaded or 44any screen saver is to be used. 45.Sh SPLASH SCREEN 46You can load and display an arbitrary bitmap image file as a welcome banner |
| 47on the screen when the system is about to start. This image will remain on 48the screen during kernel initialization process until the ``Login'' prompt 49appears on the screen or until a screen saver is loaded and initialized. 50The image will also disappear if you hit any key, although this may not work 51immediately if the kernel is still probing devices. | 47on the screen when the system is about to start. 48This image will remain on the screen 49during kernel initialization process 50until the ``Login'' prompt appears on the screen 51or until a screen saver is loaded and initialized. 52The image will also disappear if you hit any key, 53although this may not work immediately 54if the kernel is still probing devices. |
| 52.Pp 53If you specify the 54.Fl c 55or 56.Fl v 57boot option when loading the kernel, the splash image will not appear. 58However, it 59is still loaded and can be used as a screen saver later: see below. 60.Pp 61In order to display the bitmap, the bitmap file itself and the 62matching splash image decoder module must be loaded by the boot loader. 63Currently the following decoder modules are available: 64.Pp 65.Bl -tag -width splash_decoder -compact 66.It Pa splash_bmp.ko 67W*ndows BMP file decoder. 68While the BMP file format allows images of various color depths, this | 55.Pp 56If you specify the 57.Fl c 58or 59.Fl v 60boot option when loading the kernel, the splash image will not appear. 61However, it 62is still loaded and can be used as a screen saver later: see below. 63.Pp 64In order to display the bitmap, the bitmap file itself and the 65matching splash image decoder module must be loaded by the boot loader. 66Currently the following decoder modules are available: 67.Pp 68.Bl -tag -width splash_decoder -compact 69.It Pa splash_bmp.ko 70W*ndows BMP file decoder. 71While the BMP file format allows images of various color depths, this |
| 69decoder currently only handles 256 color bitmaps. Bitmaps of other color 70depths will not be displayed. | 72decoder currently only handles 256 color bitmaps. 73Bitmaps of other color depths will not be displayed. |
| 71.It Pa splash_pcx.ko 72ZSoft PCX decoder. 73This decoder currently only supports version 5 8-bpp single-plane 74images. 75.El 76.Pp 77The 78.Sx EXAMPLES --- 4 unchanged lines hidden (view full) --- 83If you enable the VESA mode support in the kernel, 84either by statically linking the VESA module or by loading the VESA module 85.Pq see Xr vga 4 , 86you can load bitmaps up to a resolution of 1024x768, depending on the VESA 87BIOS and the amount of video memory on the video card. 88.Sh SCREEN SAVER 89The screen saver will activate when the system is considered idle: i.e. 90when the user has not typed a key or moved the mouse for a specified period | 74.It Pa splash_pcx.ko 75ZSoft PCX decoder. 76This decoder currently only supports version 5 8-bpp single-plane 77images. 78.El 79.Pp 80The 81.Sx EXAMPLES --- 4 unchanged lines hidden (view full) --- 86If you enable the VESA mode support in the kernel, 87either by statically linking the VESA module or by loading the VESA module 88.Pq see Xr vga 4 , 89you can load bitmaps up to a resolution of 1024x768, depending on the VESA 90BIOS and the amount of video memory on the video card. 91.Sh SCREEN SAVER 92The screen saver will activate when the system is considered idle: i.e. 93when the user has not typed a key or moved the mouse for a specified period |
| 91of time. As the screen saver is an optional module, it must be explicitly 92loaded into memory. Currently the following screen saver modules are 93available: | 94of time. 95As the screen saver is an optional module, 96it must be explicitly loaded into memory. 97Currently the following screen saver modules are available: |
| 94.Pp 95.Bl -tag -width splash_module.ko -compact 96.It Pa blank_saver.ko 97This screen saver simply blanks the screen. 98.It Pa daemon_saver.ko 99Animated BSD Daemon screen saver. 100.It Pa fade_saver.ko 101The screen will gradually fade away. --- 98 unchanged lines hidden (view full) --- 200If the VESA support is statically linked to the kernel, it is not 201necessary to load the VESA module. 202Just load the bitmap file and the splash decoder module as in the 203first example above. 204.\".Sh DIAGNOSTICS 205.Sh CAVEATS 206Both the splash screen and the screen saver work with 207.Xr syscons 4 | 98.Pp 99.Bl -tag -width splash_module.ko -compact 100.It Pa blank_saver.ko 101This screen saver simply blanks the screen. 102.It Pa daemon_saver.ko 103Animated BSD Daemon screen saver. 104.It Pa fade_saver.ko 105The screen will gradually fade away. --- 98 unchanged lines hidden (view full) --- 204If the VESA support is statically linked to the kernel, it is not 205necessary to load the VESA module. 206Just load the bitmap file and the splash decoder module as in the 207first example above. 208.\".Sh DIAGNOSTICS 209.Sh CAVEATS 210Both the splash screen and the screen saver work with 211.Xr syscons 4 |
| 208only. They are not available for the alternative console driver | 212only. 213They are not available for the alternative console driver |
| 209.Xr pcvt 4 . 210.Sh BUGS 211If you load a screen saver while another screen saver has already 212been loaded, the first screen saver will not be automatically unloaded 213and will remain in memory, wasting kernel memory space. 214.Sh SEE ALSO 215.Xr vidcontrol 1 , 216.Xr syscons 4 , --- 28 unchanged lines hidden --- | 214.Xr pcvt 4 . 215.Sh BUGS 216If you load a screen saver while another screen saver has already 217been loaded, the first screen saver will not be automatically unloaded 218and will remain in memory, wasting kernel memory space. 219.Sh SEE ALSO 220.Xr vidcontrol 1 , 221.Xr syscons 4 , --- 28 unchanged lines hidden --- |