On Tue, 1 Mar 2005, Benjamin Herrenschmidt wrote:
On Mon, 2005-02-28 at 15:09 -0500, Michel Dänzer wrote:
On Mon, 2005-02-28 at 10:19 -0500, Alex Deucher wrote:
I think long term though, a better solution would be to get rid of
mergedfb and handle each head separately but just change the 2d/3d
On Tue, 01 Mar 2005 01:09:28 -0500, Michel Dänzer [EMAIL PROTECTED] wrote:
On Tue, 2005-03-01 at 17:02 +1100, Benjamin Herrenschmidt wrote:
On Mon, 2005-02-28 at 15:09 -0500, Michel Dänzer wrote:
On Mon, 2005-02-28 at 10:19 -0500, Alex Deucher wrote:
I think long term though, a
Vladimir Dergachev wrote:
By default r300_demo and r300_driver have tiling enabled at 16x16 pixel
squares, in fact the card should come up with this on by default..
Now on to the next question - how can one fix the 2048x2048 limit ?
check out this thread:
Roland Scheidegger wrote:
Wasn't the limit 2560x2560 with the r300 based chips? That's at least
what fglrx will do on r300.
The limit seems to be 2560 on r300 (high end) cards, but 2048 on rv300
cards (these cards really look like they have exactly the same tiling
regs as r200).
Stephane
Vladimir Dergachev wrote:
fglrx will do on r300. I'm wondering about that though a bit, that
would be 11.3 bit for coords or so ;-). It would also mean the tiling
regs need to be different a bit on r300 compared to r100/r200.
I looked through the register manual for Radeons and it looks like
On Mon, 2005-02-28 at 10:19 -0500, Alex Deucher wrote:
I think long term though, a better solution would be to get rid of
mergedfb and handle each head separately but just change the 2d/3d
engines offsets depending on which head you are rendering to. then
you wouldn't have to worry about
On Mon, 2005-02-28 at 15:09 -0500, Michel Dänzer wrote:
On Mon, 2005-02-28 at 10:19 -0500, Alex Deucher wrote:
I think long term though, a better solution would be to get rid of
mergedfb and handle each head separately but just change the 2d/3d
engines offsets depending on which head you
Hi all,
Aapo Tahkola has made a merge of our current DRM driver and latest DRM
driver from freedesktop.org.
He asked me to commit this to R300 CVS (his Internet connection is a
bit slow for this) and I would like to do it. There will be quite a few
changes as the freedesktop.org + Aapo's
Vladimir Dergachev wrote:
[snip]
Thus, could everyone with changing they have not committed yet to
*DRM* driver but plan to please let me know ? Also any comments,
reservations, etc.
One reason I am so eager for this is that there have been quite a
few fixes to the DRM driver, including
On Mon, 28 Feb 2005 16:38:05 +1100, Ben Skeggs [EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
[snip]
Thus, could everyone with changing they have not committed yet to
*DRM* driver but plan to please let me know ? Also any comments,
reservations, etc.
One reason I am so
Hopefully, the updated drm will allow me to stay in X for a while
without encountering the
WaitForSomething(): select: errno=22 error I was having with the
current drm.
One question about tiling, will this cause any problems with the current
r300 code? Or is it
something completely unrelated?
One question about tiling, will this cause any problems with the current r300
code? Or is it
something completely unrelated?
Well, Aapo has ported the patch and it worked on his computer - so it is
unlikely to cause problems. If it does we are still better off finding and
fixing the issue.
12 matches
Mail list logo
