Date: 03 May 1999 17:16:28 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Kelly Yancey <kbyanc@alcnet.com> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, freebsd-hackers@FreeBSD.ORG Subject: Re: new loader question / module question Message-ID: <xzpiuaa6v5f.fsf@flood.ping.uio.no> In-Reply-To: Kelly Yancey's message of "Mon, 3 May 1999 10:44:01 -0400 (EDT)" References: <Pine.BSF.4.05.9905031002070.53103-100000@kronos.alcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kelly Yancey <kbyanc@alcnet.com> writes: > On 3 May 1999, Dag-Erling Smorgrav wrote: > > Unfortunately, you're correct. What's more, the memory occupied by a > > module is not reclaimed when the module is unloaded. > Is there a way to free the memory allocated by the loader for the image? No. The image is a module as any other. > I'm thinking about providing a way to pass additional options to the > splash module to enable/disable certain features (hence the idea in the > original posting of using the loader to load a config file and then > locating the tag and reading the configuration). What's wrong with sysctls? > > You don't have to use BMP files; you can use PCX files instead [...] > Is this in -stable? or -current? My 3.1-19990309-STABLE machine only had > a decoder for BMP files. Both. I MFCed the PCX decoder a week or two ago. > > A PNG decoder is also planned, but it's a lot more work than a PCX > > decoder and I haven't found the time to finish it yet. > Ouch...and I was starting to feel bad for investing any more kernel > memory for something as trivial as a splash screen ;) What do you mean? The memory occupied by the decoder is inconsequential (we're talking ten kilobytes on the outside). What really eats up memory is the image, especially if you use a hi-res one (my home box has a 1024x768 splash screen). PNG images have much better compression than BMP or PCX, and will therefore occupy less memory. > Well, the first set of related patches (which I hope to have done by the > end of the week) are to add some extra video modes to the syscons driver > (320x400, 320x480, 360x200, 360x240, 360x400, and 360x480 modex). I'll > post those to -hackers when I'm done. I don't think these are really interesting, since mode X is interleaved, which makes for added complexity the decoder. It will just add complexity for no real gain. Support for mode Q, on the other hand, might be interesting for screen savers, and easy to implement. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpiuaa6v5f.fsf>