From: Christoph Hellwig <hch@lst.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mitch@0Bits.COM, Erik Andersen <andersen@codepoet.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.22-pre10-ac1 DRI doesn't work with
Date: Thu, 7 Aug 2003 16:26:24 +0200 [thread overview]
Message-ID: <20030807142624.GA29208@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0308071023040.6818-200000@logos.cnet>
> 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.
The DRM code in your tree is completly unaffected.
next prev parent reply other threads:[~2003-08-07 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 14:38 Linux 2.4.22-pre10-ac1 DRI doesn't work with Mitch
2003-08-07 11:44 ` Alan Cox
2003-08-07 13:27 ` Marcelo Tosatti
2003-08-07 14:26 ` Christoph Hellwig [this message]
2003-08-07 14:27 ` Alan Cox
2003-08-07 14:47 ` Marcelo Tosatti
2003-08-07 15:37 ` Christoph Hellwig
2003-08-07 17:23 ` Kernel 2.6.0-test2 vs 2.2.12 -- Some observations J.C. Wren
2003-08-07 17:34 ` Andrew Morton
2003-08-07 18:44 ` J.C. Wren
2003-08-08 12:16 ` Alan Cox
2003-08-07 19:23 ` Linux 2.4.22-pre10-ac1 DRI doesn't work with Erik Andersen
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 19:34 Mitch
2003-08-05 19:37 Mitch
2003-08-05 20:36 ` Erik Andersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030807142624.GA29208@lst.de \
--to=hch@lst.de \
--cc=Mitch@0Bits.COM \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox