From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: chris@pcburn.com
Cc: Gerhard Mack <gmack@innerfire.net>, linux-kernel@vger.kernel.org
Subject: Re: ati X300 support?
Date: Tue, 27 Dec 2005 23:20:45 +0000 [thread overview]
Message-ID: <200512272320.45378.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43B1BFB8.8050207@pcburn.com>
On Tuesday 27 December 2005 22:27, Chris Bergeron wrote:
> Alistair John Strachan wrote:
> >On Tuesday 27 December 2005 15:57, Gerhard Mack wrote:
> >>I have it working in X.org with no problem. I just can't get the drm
> >>module working in the kernel. Last time I tried to just add my PCI ids
> >>the problem was a lack of PCIE support in the drm drivers.
> >
> >I'd try again, I have a vague memory of reading a changelog a few releases
> > ago that mentioned PCIe support in radeon-drm.
> >
> >>FYI the fglrx drivers suck badly. ATI hasn't bothered to keep their
> >>drivers up to date at all and the result is that they finally have
> >>working 2.6.14 drivers but only for 32 bit machines. x86_64 is still
> >>broken on any recent kernel and it's been that way for months. ATI's
> >> tech support basically gave up after several days and just informed me
> >> it wasn't really supported and there is nothing they could do for me.
> >
> >You're better off running open source drivers anyway, it's less hassle,
> > you don't have to worry about every kernel upgrade breaking them, and
> > it's only an X300 anyway -- on my Mobility 9600, I just play a few small
> > games and expect OpenGL accelerated applications to work properly.
> >
> >If your goals are similar, they're probably achievable with mainline.
>
> The DRI project only supports up to the Radeon 9200 unless I missed an
> update and their page is outdated. Check the DRI ATI page for details.
>
> http://dri.freedesktop.org/wiki/ATI
Yes, you and this link are both out of date. The r300 driver provides basic
support for many newer video cards based on the r300 core and is shipped with
Xorg 7.0.0.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2005-12-27 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 23:59 Gerhard Mack
2005-12-27 1:49 ` Alistair John Strachan
2005-12-27 13:17 ` Gerhard Mack
2005-12-27 15:45 ` Alistair John Strachan
2005-12-27 15:57 ` Gerhard Mack
2005-12-27 16:03 ` Alistair John Strachan
2005-12-27 22:27 ` Chris Bergeron
2005-12-27 23:20 ` Alistair John Strachan [this message]
2005-12-28 8:28 ` Xavier Bestel
2005-12-28 17:46 ` Alistair John Strachan
2005-12-28 20:01 ` Chris Bergeron
2005-12-28 19:32 ` Kasper Sandberg
2006-01-01 19:28 ` Alistair John Strachan
2005-12-28 0:20 ` Martin Drab
2005-12-28 0:31 ` Gerhard Mack
2005-12-28 1:40 ` Martin Drab
2005-12-28 2:22 ` Gerhard Mack
2005-12-31 0:24 ` Brice Goglin
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=200512272320.45378.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=chris@pcburn.com \
--cc=gmack@innerfire.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
all inboxes | Powered by JetHome®