From: Jerome Glisse <j.glisse@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: U3 G5 AGP support patch (v4)
Date: Sun, 9 Jan 2005 21:41:44 +0100 [thread overview]
Message-ID: <4240b91605010912414a5b1b67@mail.gmail.com> (raw)
In-Reply-To: <4240b91605010909463e44bba8@mail.gmail.com>
It seems there is bug somewhere in my agp patch. I was playing with
r300 radeon and
i get a hard lockup (quite used to that while playing with r300 thought :()
But after a bit of investigation it seems to be related to agp. Right now i am
porting an old tools from dri that test agpgart & thus agp. I finally may really
need to totaly split the u3 driver from the old uninorth.
I will give a deeper look to track down the issue. In the mean time if some
one could test agp & radeon r200 on a g5. You will certainly lockup your g5
but it should not burn, at least here i just got some smoke ;)
best,
Jerome Glisse
next prev parent reply other threads:[~2005-01-09 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:26 U3 G5 AGP support patch (v4) Jerome Glisse
2005-01-09 16:06 ` Christoph Hellwig
2005-01-09 17:46 ` Jerome Glisse
2005-01-09 20:41 ` Jerome Glisse [this message]
2005-01-10 18:16 ` Jerome Glisse
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=4240b91605010912414a5b1b67@mail.gmail.com \
--to=j.glisse@gmail.com \
--cc=hch@lst.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).