From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Antonino A. Daplas" Subject: Re: [announce 0/7] fbsplash - The Framebuffer Splash Date: Wed, 9 Mar 2005 13:01:15 +0800 Message-ID: <200503091301.15832.adaplas@hotpop.com> References: <20050308015731.GA26249@spock.one.pl> Reply-To: linux-fbdev-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1D8tKT-00035N-3m for linux-fbdev-devel@lists.sourceforge.net; Tue, 08 Mar 2005 21:01:53 -0800 Received: from smtp-out.hotpop.com ([38.113.3.61]) by sc8-sf-mx1.sourceforge.net with esmtp (Exim 4.41) id 1D8tKR-0004Yg-H3 for linux-fbdev-devel@lists.sourceforge.net; Tue, 08 Mar 2005 21:01:53 -0800 Received: from hotpop.com (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 5E76EF3746D for ; Wed, 9 Mar 2005 05:01:24 +0000 (UTC) In-Reply-To: <20050308015731.GA26249@spock.one.pl> Content-Disposition: inline Sender: linux-fbdev-devel-admin@lists.sourceforge.net Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: Michal Januszewski , linux-kernel@vger.kernel.org Cc: linux-fbdev-devel@lists.sourceforge.net On Tuesday 08 March 2005 09:57, Michal Januszewski wrote: > Fbsplash - The Framebuffer Splash - is a feature that allows displaying > images in the background of consoles that use fbcon. The project is > partially descended from bootsplash. > > Unlike bootsplash, fbsplash has no in-kernel image decoder. Picture > decompression is handled by a userspace helper which provides raw image > data to the kernel. There is also no support for things like the silent > mode and progress bars, as these are best handled by userspace programs. > If splash support is really, really, really wanted in the kernel, it's probably better to just add minimal Overlay support for the framebuffer. If overlay is added, it won't be necessary to modify fbcon and the drivers, just core fb. We can have 3 levels of support. In it's most basic form, we have the display layer (what get's shown in your monitor) plus 2 buffers in system ram, the primary layer (where the console output is written) and the overlay, the static image in raw framebuffer format. Then we replace the basic framebuffer operations (imageblit, fillrect and copyarea) with ones that will read the contents of both buffers, do basic raster ops (colorkey, alpha blend, etc) before writing to the actual display buffer. The next level is both buffers are in video ram. This will need basic driver support, at least to subdivide the framebuffer memory to display, primary, and overlay. We can use the drivers accelerated drawing functions to write to the primary layer, then use software to write the processed contents to the display layer. Finally, we can enable full hardware video overlay. Tony ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click