Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266619AbUIMMcw (ORCPT ); Mon, 13 Sep 2004 08:32:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266616AbUIMMcw (ORCPT ); Mon, 13 Sep 2004 08:32:52 -0400 Received: from clock-tower.bc.nu ([81.2.110.250]:17593 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S266613AbUIMMcg (ORCPT ); Mon, 13 Sep 2004 08:32:36 -0400 Subject: Re: graphics futures - untoasted.. From: Alan Cox To: Dave Airlie Cc: Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1095074987.14359.45.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 13 Sep 2004 12:29:53 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1205 Lines: 26 On Llu, 2004-09-13 at 13:10, Dave Airlie wrote: > So what are peoples view on doing the following to the radeon driver after > Alan has showed the code... I've not had time to test it but I just posted the code as-is since thats probably the best way right now > Now I know someone might say that we probably don't need a common layer, > that with Alans scheme the fb can call the drm and the drm the fb, but if > this happens then you start mandating the fb be loaded for certain DRM > things and vice-versa, Agreed - it will depend on the card, and on what makes sense for other reasons. Memory manager code may also need to be part of that. The code I posted has no provision for "common" module, but just add it to the list and it'll hopefully DTRT. Providing the DRI and FB drivers reference symbols in the common module it'll also autoload properly. Let me know what you think of the code so far (however bad) and I'll try and get it ticking nicely. - 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/