From: Daniel Pittman <daniel@rimspace.net>
To: linux-kernel@vger.kernel.org
Subject: Re: To Anyone with a Radeon 7500 board and the ali developer
Date: Tue, 17 Sep 2002 11:33:11 +1000 [thread overview]
Message-ID: <8765x5z9go.fsf@enki.rimspace.net> (raw)
In-Reply-To: <20020916.121423.109699832.davem@redhat.com> ("David S. Miller"'s message of "Mon, 16 Sep 2002 12:14:23 -0700 (PDT)")
On Mon, 16 Sep 2002, David S. Miller wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Date: 16 Sep 2002 13:42:11 +0100
>
> What is sad is the is an AGP standardised way to read this and
> XFree86 still, all these years on, doesn't do it by default.
>
> Totally agreed.
>
> I have even suggested on the xfree86 developer list at least 2 times
> that they do this to choose the default, but they claim it isn't the
> right thing to do.
>
> So people's boxes will keep hanging and xfree86 DRM will continue to
> be a support nightmare.
...which might explain why my machine has occasional DRM related hangs,
since there is no way for me to match the XFree86 AGP speed and the BIOS
set AGP speed -- my BIOS will not tell me what it set, nor does it have
a toggle to adjust it.
Does some tool already exist that can query this information from
userspace? If not, are the specifications needed to build one freely
available?
Daniel
--
Now that mountains of meaningless words and oceans divide us
And we each have our own set of stars to comfort and guide us
-- Nick Cave, _Come Into My Sleep_
next prev parent reply other threads:[~2002-09-17 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 4:26 To Anyone with a Radeon 7500 board and the ali developer Alex Davis
2002-09-16 5:01 ` David S. Miller
2002-09-16 12:42 ` Alan Cox
2002-09-16 19:14 ` David S. Miller
2002-09-17 1:33 ` Daniel Pittman [this message]
2002-09-17 1:29 ` David S. Miller
2002-09-17 4:18 ` Daniel Pittman
2002-09-19 23:35 ` Nicholas
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 0:30 Nicholas
2002-09-16 4:52 ` David S. Miller
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=8765x5z9go.fsf@enki.rimspace.net \
--to=daniel@rimspace.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