From: Dave Airlie <airlied@linux.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan McDowell <noodles@earth.li>,
xorg-driver-ati@lists.x.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-rc3 + RS690 + DRM + xf86-video-ati hang
Date: Tue, 4 Mar 2008 09:24:08 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.0.82.0803040919370.22945@skynet.skynet.ie> (raw)
In-Reply-To: <20080304011332.639a0551.akpm@linux-foundation.org>
> > results in a machine that boots to GDM successfully. Likewise if I
> > disable CONFIG_DRM_RADEON in 2.6.25-rc3 the machine boots to GDM ok.
>
> is what we wanted to know, thanks. Surely it's a plain old regression?
Nope, its a userspace driver problem.. we have not released
non-experimental code for that chipset, so its not surprising it fails
when the kernel code gets run, but the fix most likely is in userspace not
in the kernel.
I could disable the userspace DRI code but then where would I find my
testers .. if he reads his Xorg log it says DRI is experimental on rs690
and not to come crying..
this is the problem with adding new chipsets, I either wait for 6 months
for all the bugs to get kicked out so nobody wins, or I push it upstream
so most people win, I could back this out of the kernel, but experimental
userspace code isn't a reason for this..
Dave.
next prev parent reply other threads:[~2008-03-04 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 19:35 2.6.25-rc3 + RS690 + DRM + xf86-video-ati hang Jonathan McDowell
2008-03-02 19:23 ` Alex Deucher
2008-03-04 6:48 ` Andrew Morton
2008-03-04 8:16 ` Dave Airlie
2008-03-04 8:51 ` Jonathan McDowell
2008-03-04 9:13 ` Andrew Morton
2008-03-04 9:24 ` Dave Airlie [this message]
2008-03-04 10:33 ` Jonathan McDowell
2008-03-04 11:23 ` Dave Airlie
2008-03-04 17:13 ` JoJo jojo
2008-03-04 18:02 ` Alex Deucher
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=alpine.DEB.0.82.0803040919370.22945@skynet.skynet.ie \
--to=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noodles@earth.li \
--cc=xorg-driver-ati@lists.x.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;
as well as URLs for NNTP newsgroup(s).