Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263228AbUAIRRV (ORCPT ); Fri, 9 Jan 2004 12:17:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263260AbUAIRRV (ORCPT ); Fri, 9 Jan 2004 12:17:21 -0500 Received: from iron-c-1.tiscali.it ([212.123.84.81]:12577 "EHLO mailr-1.tiscali.it") by vger.kernel.org with ESMTP id S263228AbUAIRRS (ORCPT ); Fri, 9 Jan 2004 12:17:18 -0500 Date: Fri, 9 Jan 2004 18:17:33 +0100 From: Kronos To: James Simmons Cc: Linux Fbdev development list , Linux Kernel Mailing List Subject: Re: [Linux-fbdev-devel] New FBDev patch Message-ID: <20040109171733.GA13027@dreamland.darkstar.lan> Reply-To: kronos@kronoz.cjb.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1288 Lines: 36 Il Thu, Jan 08, 2004 at 10:03:54PM +0000, James Simmons ha scritto: > > This is the latest patch against 2.6.0-rc3. Give it a try. > > http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz > (03/09/17 1.1267.40.1) > Add new API framebuffer_alloc and framebuffer_release. > > Framebuffer info structure (ie. struct fb_info) must be obtained from > framebuffer_alloc. When it is no longer needed (after unregister_framebuffer > and clean up) it can be released using framebuffer_release. > > If the framebuffer is not registered yet (eg. on error path) then fb_info must > be released via kfree. Are we sure that we want this for 2.6? Greg KH has a much less intrusive patch, maybe you should take that instead and keep my work 2.7. If you decide to go with framebuffer_alloc then I have more patches for you ;) Luca -- Reply-To: kronos@kronoz.cjb.net Home: http://kronoz.cjb.net I went to God just to see And I was looking at me Saw heaven and hell were lies When I'm God everyone dies - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/