Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264305AbUAIUHA (ORCPT ); Fri, 9 Jan 2004 15:07:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264583AbUAIUHA (ORCPT ); Fri, 9 Jan 2004 15:07:00 -0500 Received: from phoenix.infradead.org ([213.86.99.234]:62218 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S264305AbUAIUGL (ORCPT ); Fri, 9 Jan 2004 15:06:11 -0500 Date: Fri, 9 Jan 2004 20:06:06 +0000 (GMT) From: James Simmons To: Kronos cc: Linux Fbdev development list , Linux Kernel Mailing List Subject: Re: [Linux-fbdev-devel] New FBDev patch In-Reply-To: <20040109171733.GA13027@dreamland.darkstar.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1067 Lines: 29 > > 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 ;) I have been using it for awhile on various cards. - 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/