I just updated the tool to (hopefully) calculate the AGP aperture address and
size dynamically. I'm using some code borrowed from REnouveau.
I haven't tested this yet, but it should work.
Again, if anyone is using this I'd like to get feedback on what features would
be useful. Currently I plan to
>
> Dave, how did you generate this file? (Was it from an indirect buffer?)
> http://www.skynet.ie/~airlied/dri/mypa.parsed
Magic and guess work produced that file...
Basically I used glxtest which works fine to dump the maps just actually
finding the IB is a lot more impossible.. I search for
Oliver,
On 4/26/07, Oliver McFadden <[EMAIL PROTECTED]> wrote:
>
> Currently this is hard-coded, because I haven't done dynamic calculation of
> those variables yet.
>
> You can determine REG_ADDR from "lspci -v"; you want the line that matches
> "(32-bit, non-prefetchable) [size=64K]". In the fol
On 4/26/07, Phillip Ezolt <[EMAIL PROTECTED]> wrote:
> Oliver & Dave,
>
> >
> > You maybe have missed out on #dri-devel on freenode irc, it works
> > reasonably well for getting insta-answers depending on timezone etc..
>
> Ah. I HAVE missed that. I'll have to hang out there. I usually have
> th
Oliver & Dave,
>
> You maybe have missed out on #dri-devel on freenode irc, it works
> reasonably well for getting insta-answers depending on timezone etc..
Ah. I HAVE missed that. I'll have to hang out there. I usually have
the wireless network turned off when I'm X hacking, but this gives me
On 4/23/07, Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> >
> >> I just started reading the X code about 6 months ago, and the learning
> >> curve has been steep. My emails to dri-devel are answered now and
> >> again, and that is kinda frustrating when you want an answer NOW.
>
> You maybe have miss
>
>> I just started reading the X code about 6 months ago, and the learning
>> curve has been steep. My emails to dri-devel are answered now and
>> again, and that is kinda frustrating when you want an answer NOW.
You maybe have missed out on #dri-devel on freenode irc, it works
reasonably well
On Mon, Apr 23, 2007 at 07:38:45PM +, Oliver McFadden wrote:
> On 4/23/07, Phillip Ezolt <[EMAIL PROTECTED]> wrote:
> > Awesome.
> >
> > As an aside, I would really like to make it easier for other people to
> > hack on radeon & X.
> > I've been fighting with my Radeon 200M for months, hacking
On 4/23/07, Phillip Ezolt <[EMAIL PROTECTED]> wrote:
> Awesome.
>
> As an aside, I would really like to make it easier for other people to
> hack on radeon & X.
> I've been fighting with my Radeon 200M for months, hacking when I have
> spare time.
I think we have similar goals here. I'm doing this
On 4/23/07, Phillip Ezolt <[EMAIL PROTECTED]> wrote:
> Oliver,
> I've been hacking on the RS480 (Radeon 200M) for a while, and Dave
> has (aweseomely) brought it to a point where it has the working GART,
> and a limping Mesa.
>
> Currently triangles are broken, and I have a very simple test case
I've previously filed a bug report (bug #10211) about the
R300_RB3D_DSTCACHE_CTLSTAT issue, however I couldn't prove the proposed patch
was correct. I've investigated this further and I can confirm that the blob
indeed writes 0xa to R300_RB3D_DSTCACHE_CTLSTAT before 3D operations, and 0x2
after 3D
11 matches
Mail list logo
