public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hartmann <jhartmann@valinux.com>
To: "Michael D. Crawford" <crawford@goingware.com>
Cc: linux-kernel@vger.kernel.org, newbie@xfree86.org
Subject: Re: DRI doesn't work on 2.4.0 but does on prerelease-ac5
Date: Sun, 07 Jan 2001 12:11:24 -0700	[thread overview]
Message-ID: <3A58BF5C.1090505@valinux.com> (raw)
In-Reply-To: <3A57A83B.702CEC98@goingware.com>


> Could XFree86 4.0.2 fix this?  I had been waiting until the binary packages were
> available from ftp.slackware.com because Patrick Volkerding lays out the
> directories in a slightly different manner that he argues pretty convincingly is
> preferable, but it would be a drag for me to reproduce by building it myself.

XFree 4.0.2 will fix this.

> (EE) r128(0): R128DRIScreenInit failed (DRM version = 2.1.2, expected 1.0.x). 
> Disabling DRI.

We made binary incompatible device interface changes with 4.0.2.  These 
driver changes resulted in a more stable / faster / cleaner Rage 128 driver.

-Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-07 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 23:20 DRI doesn't work on 2.4.0 but does on prerelease-ac5 Michael D. Crawford
2001-01-07  3:30 ` Alan Olsen
2001-01-07  4:53   ` [Newbie]Re: " dep
2001-01-07 17:55   ` Dax Kelson
2001-01-07 19:11 ` Jeff Hartmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 18:35 Michael D. Crawford
2001-01-08 22:06 ` Bill Nottingham
2001-01-08 22:55 ` khromy
2001-01-08 22:45 Michael D. Crawford
2001-01-09 16:17 ` Ragnar Hojland Espinosa
2001-01-10  4:21 Bill Crawford
2001-01-10  4:37 ` Alan Cox
2001-01-10  5:18   ` Alan Olsen
2001-01-10 13:02 Gareth Hughes

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=3A58BF5C.1090505@valinux.com \
    --to=jhartmann@valinux.com \
    --cc=crawford@goingware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=newbie@xfree86.org \
    /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