Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 29 Oct 2002 16:24:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 29 Oct 2002 16:24:03 -0500 Received: from falcon.mail.pas.earthlink.net ([207.217.120.74]:9463 "EHLO falcon.mail.pas.earthlink.net") by vger.kernel.org with ESMTP id ; Tue, 29 Oct 2002 16:24:02 -0500 Date: Tue, 29 Oct 2002 14:23:34 -0800 (PST) From: James Simmons X-X-Sender: To: Christoph Hellwig cc: Linus Torvalds , Linux Kernel Mailing List , Linux Fbdev development list Subject: Re: [BK updates] fbdev changes updates. In-Reply-To: <20021029211800.A2806@infradead.org> 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: 1362 Lines: 33 > > > On Tue, Oct 29, 2002 at 12:46:16PM -0800, James Simmons wrote: > > > > > > > > OOps. Forgot the link. > > > > > > > > bk://fbdev.bkbits.net/fbdev-2.5 > > > > > > Does it still contain the random file movearounds? > > > > The reason I did this was to prevent adding another chuck of agp code. The > > current work around for AGP fbdev drivers to have there OWN AGP code. So > > we can leave the agp drivers where they are at or the framebuffer layer > > can have its own AGP code for itself. Which way do you think it should be > > done? > > > > 1) Fbdev layer has it own AGP layer > > > > 2) Use already existing AGP layer code. > > Well, I'd be very happy if you could separate different things abit. > Everyone wants the console fixes in, but code placement is a bit more of a > policy issue and wants more discussion.. Even when they are in different > directories the drm drivers can always call into the fbdev drivers as "base > modules", like sis currently does. Fair enough. I'm moving agp and dri back to drivers/char. I would like to discuss a solution to how to initialize the AGP code quicker :-) - 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/