mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mitch@0Bits.COM
Cc: Erik Andersen <andersen@codepoet.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.22-pre10-ac1 DRI doesn't work with
Date: 07 Aug 2003 12:44:09 +0100	[thread overview]
Message-ID: <1060256649.3169.20.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0308061521430.22986@mx.homelinux.com>

On Mer, 2003-08-06 at 15:38, Mitch@0Bits.COM wrote:
> I think with the new vmap changes that went in in -pre7 means
> you will need to get a new drm module (like from X cvs or
> http://dri.sourceforge.net/downloads.phtml) and recompile it
> with the new kernel headers which will then pick up the define
> -DVMAP_4_ARGS in the Makefile and give you a good module that works.
> 
> The DRI kernel trees need updating.

That doesn't seem a 2.4.22 candidate thing to me. If vmap broke the DRI
then the vmap patch wants reverting for 2.4.22 IMHO, and looking at for
2.4.23.


  reply	other threads:[~2003-08-07 11:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 14:38 Mitch
2003-08-07 11:44 ` Alan Cox [this message]
2003-08-07 13:27   ` Marcelo Tosatti
2003-08-07 14:26     ` Christoph Hellwig
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=1060256649.3169.20.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Mitch@0Bits.COM \
    --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

all inboxes | Powered by JetHome®