From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: drm bugs hopefully fixed but there might still be one..
Date: Thu, 24 Mar 2005 09:02:03 -0800 [thread overview]
Message-ID: <200503240902.03808.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503241015190.7647@skynet>
On Thursday, March 24, 2005 2:33 am, Dave Airlie wrote:
> Hi Andrew, Dave,
>
> I've put a couple of patches into my drm-2.6 tree that hopefully fix up
> the multi-bridge on i915 and the XFree86 4.3 issue.. Andrew can you drop
> the two patches in your tree.. the one from Brice and the one I attached
> to the bug? you'll get conflicts anyway I'm sure. I had to modify Brices
> one as it didn't look safe to me in all cases..
>
> I think their might be one left, but I think it only seems to be on
> non-intel AGP system, as in my system works fine for a combination of
> cards and X releases ... anyone with a VIA chipset and Radeon graphics
> card or r128 card.. testing the next -mm would help me a lot..
I'm trying to get ahold of one--so hopefully I'll be able to test and fix this
stuff up when I do.
Jesse
next prev parent reply other threads:[~2005-03-24 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 10:33 drm bugs hopefully fixed but there might still be one Dave Airlie
2005-03-24 11:04 ` Andrew Morton
2005-03-24 17:02 ` Jesse Barnes [this message]
2005-03-24 18:18 ` Dave Jones
2005-03-24 18:35 ` Jesse Barnes
2005-03-24 21:58 ` cliff white
2005-03-24 22:21 ` Andrew Morton
2005-03-24 23:04 ` cliff white
2005-03-24 23:12 ` Andrew Morton
[not found] <3LxV3-5Is-25@gated-at.bofh.it>
[not found] ` <3LE0y-2Kn-55@gated-at.bofh.it>
[not found] ` <3LFg5-3MJ-37@gated-at.bofh.it>
[not found] ` <3LFzj-40t-15@gated-at.bofh.it>
2005-03-24 20:09 ` Jean Delvare
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=200503240902.03808.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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