From: Keenan Pepper <keenanpepper@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: i830 DRM problems
Date: Mon, 21 Mar 2005 20:07:21 -0500 [thread overview]
Message-ID: <423F6FC9.4080807@gmail.com> (raw)
In-Reply-To: <423F5A0A.7060307@ens-lyon.org>
> Sorry about that, we start to talk about it in private with Dave.
> But, I did not really it since Keenan Pepper told me it was due
> to a bug in the XFree 4.3 driver.
> I am now using Xorg and didn't see any DRM problem since.
> However, I can't confirm that my bug was surely due to the XFree driver
> and not to the kernel driver since Xorg uses i915 instead of i830.
> Keenan, do you have details ?
Yes, I talked to Alan Hourihane about it and he identified it as a
memory allocation bug in the i810 X server driver. It's not related to
DRI - it happens even with DRI turned off - so it wouldn't matter which
DRM module is being used.
prev parent reply other threads:[~2005-03-22 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 13:41 i830 DRM problems Brice Goglin
2005-03-11 23:07 ` Dave Airlie
2005-03-21 23:14 ` Andrew Morton
2005-03-21 23:34 ` Brice Goglin
2005-03-22 0:13 ` Andrew Morton
2005-03-22 12:01 ` Brice Goglin
2005-03-22 1:07 ` Keenan Pepper [this message]
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=423F6FC9.4080807@gmail.com \
--to=keenanpepper@gmail.com \
--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