public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Egbert Eich <eich@suse.de>
Cc: Andi Kleen <ak@suse.de>,
	Thomas Zehetbauer <thomasz@hostmaster.org>,
	linux-kernel@vger.kernel.org, idr@us.ibm.com
Subject: Re: status of DRM_MGA on x86_64
Date: Mon, 1 Nov 2004 21:16:43 +1100	[thread overview]
Message-ID: <21d7e99704110102161132d37b@mail.gmail.com> (raw)
In-Reply-To: <16774.1839.343824.305232@suse.de>

> 
> I solved it for RADEON, MGA and R128.
> It would be interesting to solve this for the i915 driver, too,
> and possibly some others.
> 
> That it hasn't been merged into DRI yet is a shame. Appearantly
> nobody has ever realized why this stuff is useful. Unfortunately
> I don't have the time for lobbying it.
> It's a very boring undertaking to have to port this from one DRI
> version to the next.

Ian, can you look at this I think you are the best person (maybe
Keithw) to tell whether this stuff breaks compat in any direction,.
Egbert you may not want to lobby for it but all I personally want to
know is what it might potentially break in terms of backwards
compatiblity.... from SuSEs point of view as long as a distro is
consistent then you are okay, for us the whole keeping DRIs built
against older kernels working with newer kernels is the only real
issue...

Hopefully Ian can look at the patch and decide on it....

Dave.

Dave.

  reply	other threads:[~2004-11-01 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1099052450.11282.72.camel@hostmaster.org.suse.lists.linux.kernel>
     [not found] ` <1099061384.11918.4.camel@hostmaster.org.suse.lists.linux.kernel>
     [not found]   ` <41829E39.1000909@us.ibm.com.suse.lists.linux.kernel>
     [not found]     ` <1099097616.11918.26.camel@hostmaster.org.suse.lists.linux.kernel>
2004-10-30  1:56       ` status of DRM_MGA on x86_64 Andi Kleen
     [not found]         ` <21d7e99704103004155d2826fb@mail.gmail.com>
2004-10-30 11:17           ` Dave Airlie
2004-10-30 18:08             ` Thomas Zehetbauer
2004-11-01  9:51         ` Egbert Eich
2004-11-01 10:16           ` Dave Airlie [this message]
2004-11-01 13:48             ` Egbert Eich
     [not found] <1099052450.11282.72.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
     [not found] ` <1099061384.11918.4.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
     [not found]   ` <41829E39.1000909@us.ibm.com.suse.lists.linux.kernel.suse.lists.linux.kernel>
     [not found]     ` <1099097616.11918.26.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
     [not found]       ` <p734qkd0y0n.fsf@verdi.suse.de.suse.lists.linux.kernel>
     [not found]         ` <21d7e99704103004155d2826fb@mail.gmail.com.suse.lists.linux.kernel>
     [not found]           ` <21d7e997041030041748b60ce7@mail.gmail.com.suse.lists.linux.kernel>
2004-10-30 13:57             ` Andi Kleen
2004-10-29 12:20 Thomas Zehetbauer
2004-10-29 14:49 ` Thomas Zehetbauer
2004-10-29 19:47   ` Ian Romanick
2004-10-30  0:53     ` Thomas Zehetbauer

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=21d7e99704110102161132d37b@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=ak@suse.de \
    --cc=eich@suse.de \
    --cc=idr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomasz@hostmaster.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