Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 19 Feb 2002 20:40:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 19 Feb 2002 20:40:50 -0500 Received: from traven.uol.com.br ([200.231.206.184]:3986 "EHLO traven.uol.com.br") by vger.kernel.org with ESMTP id ; Tue, 19 Feb 2002 20:40:43 -0500 Date: Tue, 19 Feb 2002 22:40:00 -0300 (BRT) From: Jean Paul Sartre To: Alan Cox cc: Linux Kernel Mailing List Subject: Re: sis_malloc / sis_free In-Reply-To: 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 On Wed, 20 Feb 2002, Alan Cox wrote: > Date: Wed, 20 Feb 2002 01:51:15 +0000 (GMT) > From: Alan Cox > To: Jean Paul Sartre > Cc: Linux Kernel Mailing List > Subject: Re: sis_malloc / sis_free > > > 'shares' code with the fb code. What if I have SIS framebuffer disabled > > and SIS DRM code enabled? In 2.4.18-rc2, the SIS DRM code does not compile > > from the lack of sis_malloc and sis_free function. > > SIS DRM requires the SIS frame buffer. But this is a 'semantic' mode of requiring. The 'requirement' does not apply in the source, as I saw (or it'd compile normally with the DRM code, and FB code gives sis_malloc and sis_free (try grepping sis_malloc in drivers/char/sis, please)). - 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/