Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275351AbTHGOpj (ORCPT ); Thu, 7 Aug 2003 10:45:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275355AbTHGOpj (ORCPT ); Thu, 7 Aug 2003 10:45:39 -0400 Received: from proibm3.portoweb.com.br ([200.248.222.108]:51658 "EHLO portoweb.com.br") by vger.kernel.org with ESMTP id S275351AbTHGOpV (ORCPT ); Thu, 7 Aug 2003 10:45:21 -0400 Date: Thu, 7 Aug 2003 11:47:53 -0300 (BRT) From: Marcelo Tosatti X-X-Sender: marcelo@logos.cnet To: Christoph Hellwig cc: Alan Cox , , Erik Andersen , Linux Kernel Mailing List Subject: Re: Linux 2.4.22-pre10-ac1 DRI doesn't work with In-Reply-To: <20030807142624.GA29208@lst.de> 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: 895 Lines: 27 On Thu, 7 Aug 2003, Christoph Hellwig wrote: > > I dont understand how the vmap change can break DRM. > > > > The vmap patch only changes internal mm/vmalloc.c code (vmalloc() call > > acts exactly the same way as before AFAICS). > > > > Anyway, Mitch (or Erik who's seeing the problem), can please revert the > > vmap() change to check if its causing the mentioned problem? > > vmap() doesn't break DRM. The external drm code just detects that > vmap is present and then uses the new interface, but this new code > also expects a new exported symbol. And which symbol is that? > The DRM code in your tree is completly unaffected. Fine. - 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/