From: Dave Airlie <airlied@gmail.com>
To: Nix <nix@esperi.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why no XML in the Kernel?
Date: Thu, 6 Oct 2005 08:57:26 +1000 [thread overview]
Message-ID: <21d7e9970510051557u42ae32f0rca46e951c5da536f@mail.gmail.com> (raw)
In-Reply-To: <87br23odls.fsf@amaterasu.srvr.nix>
> >
> > This is just mach64, we don't have mach64 support in the kernel so it
> > has nothing to do with the kernel... I've no idea why mach64 broke but
>
> I misspoke. Some of the non-DRM API changes around 2.6.12 broke the
> 6.8.2 mach64 module in DRI CVS; the development version builds again,
> and nearly works.
>
But that's my point if you had a previously working mach64 with 6.8.2
with a DRM from around then, and a kernel upgrade broke the DRM you
should be just able to upgrade the DRM to the latest DRM CVS, there
isn't any such thing as a 6.8.2 DRM, you'll only cause much more
issues trying to fix an issue in the kernel side by also
simultaneously upgrading userspace... as you've no fixed working point
to try from..
The mach64 drm is in CVS on cvs.freedesktop.org:/cvs/dri and the module is drm..
Dave.
next prev parent reply other threads:[~2005-10-05 22:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:41 Ahmad Reza Cheraghi
2005-10-02 9:50 ` Nick Piggin
2005-10-02 11:02 ` James Courtier-Dutton
2005-10-02 10:37 ` Nick Piggin
2005-10-02 11:57 ` Bas Westerbaan
2005-10-02 11:09 ` James Bruce
2005-10-02 13:47 ` Willy Tarreau
2005-10-03 19:21 ` Bill Davidsen
2005-10-02 18:53 ` Jon Masters
2005-10-03 15:08 ` Nix
2005-10-03 15:35 ` Al Viro
2005-10-03 19:47 ` Nix
2005-10-03 19:56 ` linux-os (Dick Johnson)
2005-10-05 21:11 ` Dave Airlie
2005-10-05 21:31 ` Nix
2005-10-05 22:57 ` Dave Airlie [this message]
2005-10-05 23:07 ` Nix
2005-10-05 23:36 ` Dave Airlie
2005-10-05 22:22 ` jmerkey
2005-10-05 23:46 ` Dave Airlie
2005-10-07 22:14 ` Matan Ziv-Av
2005-10-02 21:55 ` Martin J. Bligh
2005-10-03 4:45 ` Nick Piggin
2005-10-08 1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand
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=21d7e9970510051557u42ae32f0rca46e951c5da536f@mail.gmail.com \
--to=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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®