http://bugs.freedesktop.org/show_bug.cgi?id=26745
Summary: mach64 driver missing 32-bit ioctl compatibility
routines
Product: DRI
Version: XOrg CVS
Platform: SPARC
OS/Version: Linux (All)
Status: NEW
On Tue, Feb 9, 2010 at 10:15 AM, Alex Deucher alexdeuc...@gmail.com wrote:
You might check if your bios has an option to enable an irq for vga
devices. You'll need an irq for vblank support, but beyond that I
don't recall what else the mach64 could use irqs for.
Unfortunately, no such option
at c000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 2
I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
Perhaps that's just the size of the window but only 8M is physically
present.
I have compiled the kernel mach64 DRM driver from Archlinux
compiled the kernel mach64 DRM driver from Archlinux, posted by
Alexander Lam (many thanks for that), and it seems I can enable DRI
with 1024x768x16, but I get the following (EE):
(II) MACH64(0): [DRI] installation complete
(II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
(II) MACH64(0
just the size of the aperture. The driver will detect the
proper amount of vram installed.
I have compiled the kernel mach64 DRM driver from Archlinux, posted by
Alexander Lam (many thanks for that), and it seems I can enable DRI
If one of you can port it to the latest kernel bits, we could
is physically
present.
The 16MB is split into two apertures. They both point to the same memory
area but the byte swapping for each can be controlled independently.
You can actually have 16MB of memory on a Rage Pro but the CPU can't
directly access all of it.
I have compiled the kernel mach64 DRM
Hello,
I am interested in getting DRI working on my ATI Rage XL card under
2.6.31-14 with mach64_drv 6.8.2 (Xorg 1.6.3 from Ubuntu Karmic koala).
Git says that the mach64 driver was deleted, along with shared-code,
linux-core, etc, in commit 9dd361. Do these drivers live anywhere else
now? Has
On Sun, Feb 7, 2010 at 1:32 AM, Catalin Patulea c...@vv.carleton.ca wrote:
Hello,
I am interested in getting DRI working on my ATI Rage XL card under
2.6.31-14 with mach64_drv 6.8.2 (Xorg 1.6.3 from Ubuntu Karmic koala).
Git says that the mach64 driver was deleted, along with shared-code
On Sun, Feb 7, 2010 at 1:32 AM, Catalin Patulea c...@vv.carleton.ca wrote:
Hello,
I am interested in getting DRI working on my ATI Rage XL card under
2.6.31-14 with mach64_drv 6.8.2 (Xorg 1.6.3 from Ubuntu Karmic koala).
Git says that the mach64 driver was deleted, along with shared-code
that the mach64 driver was deleted, along with shared-code,
linux-core, etc, in commit 9dd361. Do these drivers live anywhere else
now? Has anyone tried compiling them against a recent kernel?
They live in the kernel.
Except for mach64 :-) Unless I'm mistaken, that never made it into the
linux
Except for mach64 :-) Unless I'm mistaken, that never made it into the
linux kernel.
If someone wants to add mach64 to staging it would be possible, it would
be nice if clean patches that pass checkpatch.pl could be constructed for
it.
Since I think all the security issues were resolved
2010/2/7 Kristian Høgsberg k...@bitplanet.net:
They live in the kernel.
I can't seem to find them there.. perhaps I'm looking in the wrong place:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/gpu/drm
http://bugs.freedesktop.org/show_bug.cgi?id=21945
had...@gmx.de changed:
What|Removed |Added
CC||had...@gmx.de
--- Comment #1 from
http://bugs.freedesktop.org/show_bug.cgi?id=787
ajax at nwnk dot net a...@nwnk.net changed:
What|Removed |Added
Version|CVS |git
--- Comment
http://bugs.freedesktop.org/show_bug.cgi?id=7260
ajax at nwnk dot net a...@nwnk.net changed:
What|Removed |Added
Version|CVS |git
--- Comment
http://bugs.freedesktop.org/show_bug.cgi?id=6412
ajax at nwnk dot net a...@nwnk.net changed:
What|Removed |Added
Version|CVS |git
--- Comment
http://bugs.freedesktop.org/show_bug.cgi?id=7790
ajax at nwnk dot net a...@nwnk.net changed:
What|Removed |Added
Version|CVS |git
--- Comment
http://bugs.freedesktop.org/show_bug.cgi?id=21945
Summary: mach64 DRI driver hangs machine on X server startup
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
So marcheu reminded me of my laziness and I built mach64 but I took a
quick look at its API and its not 32/64 compliant by any reach.
So I'd like to merge it with a version 3.0.0 API which fixes all the API
issues I could fine, mainly using void *, unsigned long, I nuked some
unsigned
On Wed, 2009-02-04 at 04:42 -0800, Dave Airlie wrote:
So marcheu reminded me of my laziness and I built mach64 but I took a
quick look at its API and its not 32/64 compliant by any reach.
So I'd like to merge it with a version 3.0.0 API which fixes all the API
issues I could fine
http://bugs.freedesktop.org/show_bug.cgi?id=16812
--- Comment #2 from Olivier Valentin [EMAIL PROTECTED] 2008-07-24 04:47:48
PST ---
I located the failing condition in shared-core/mach64_dma.c:1652, from what I
understand, the code waits up to 1 second to acquire a free message structure
a specific DRI driver from git code, the building process
also creates an up to date version of the drm.ko module. And your mach64 module
depends on this new version.
2) The mach64 drm module is not bundled in many distros so, when you install
the mach64.ko, it has no previous version in your /lib
http://bugs.freedesktop.org/show_bug.cgi?id=16812
Summary: X hang at random while using GL app with mach64 with
timeout waiting for buffers
Product: DRI
Version: DRI CVS
Platform: Other
OS/Version: All
Status: NEW
http://bugs.freedesktop.org/show_bug.cgi?id=16812
--- Comment #1 from Olivier Valentin [EMAIL PROTECTED] 2008-07-23 01:25:28
PST ---
I said screen goes black... I was wrong, it just freezes and I still see the
last image of my game.
It happens even using XAA.
There is nothing special at
||FIXED
--- Comment #2 from mitch074 [EMAIL PROTECTED] 2008-06-12 14:05:55 PST ---
Pinging this bug again, new progress:
- with the X server provided with Xubuntu 8.04, a recent drm.ko compiled from
a fresh git extract, the distro-provided 6.8.0 mach64 driver, and 16
http://bugs.freedesktop.org/show_bug.cgi?id=7155
--- Comment #1 from mitch074 [EMAIL PROTECTED] 2008-04-30 13:51:44 PST ---
Pinging this bug, I have similar hardware IBM Thinkpad with Rage Mobility
M1/8Mb (AGP, mach64 core with texel unit); symptoms remain with latest 6.8.0
ati driver
On Sun, 02 Dec 2007 20:59:16 +, José Fonseca wrote:
On Fri, 23 Nov 2007 00:27:37 +0100, Pascal Vincent wrote:
Hello,
can you please indicate the current ATI mach64 DRI status. In fact,
http://dri.freedesktop.org/wiki/ATIMach64 page is not so clear so i
don't have the clear responses
On Fri, 23 Nov 2007 00:27:37 +0100, Pascal Vincent wrote:
Hello,
can you please indicate the current ATI mach64 DRI status. In fact,
http://dri.freedesktop.org/wiki/ATIMach64 page is not so clear so i
don't have the clear responses to - is mach64 is now secure ? this means
Jesse Barnes a écrit :
I think this bit might cause problems. Since it doesn't look like
you're using a hardware provided vblank count register, you'll want to
keep vblank interrupts on after the first enable call so that it'll
keep getting incremented in mach64_driver_irq_handler(),
On Thursday, November 01, 2007 11:24 Mathieu Bérard wrote:
Jesse Barnes a écrit :
I think this bit might cause problems. Since it doesn't look like
you're using a hardware provided vblank count register, you'll want
to keep vblank interrupts on after the first enable call so that
it'll
Jesse Barnes a écrit :
Forgive my lack of global understanding of the whole issue but my
conclusion is that we just can't disable vbl interrupt on hardware
which lack vbl count in hardware, right ?
That's one option, yes.
The other option is to calculate how many vblank interrupts
On Thursday, November 01, 2007 12:06 Mathieu Bérard wrote:
Jesse Barnes a écrit :
Forgive my lack of global understanding of the whole issue but my
conclusion is that we just can't disable vbl interrupt on hardware
which lack vbl count in hardware, right ?
That's one option, yes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Barnes wrote:
The other option is to calculate how many vblank interrupts have
occurred between off and on periods. You could do this by recording
the time when interrupts were disabled, figuring out how much time has
passed between
Hi,
here is a patch that port the mach64 drm driver to vblank rework.
It does not seems to cause any regression on my Rage Mobility P/M
--
Mathieu Bérard
diff --git a/linux-core/mach64_drv.c b/linux-core/mach64_drv.c
index 9709934..16bc9ff 100644
--- a/linux-core/mach64_drv.c
+++ b/linux-core
On Wednesday, October 31, 2007 3:12 Mathieu Bérard wrote:
+void mach64_disable_vblank(struct drm_device * dev, int crtc)
+{
+ drm_mach64_private_t *dev_priv = dev-dev_private;
u32 status = MACH64_READ(MACH64_CRTC_INT_CNTL);
- DRM_DEBUG(before install CRTC_INT_CTNL:
http://bugs.freedesktop.org/show_bug.cgi?id=11250
--- Comment #4 from [EMAIL PROTECTED] 2007-06-13 16:36 PST ---
*** Bug 11251 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
http://bugs.freedesktop.org/show_bug.cgi?id=11250
--- Comment #5 from [EMAIL PROTECTED] 2007-06-13 16:37 PST ---
*** Bug 11252 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
Hi,
I'd like to upstream the mach64 drm at some point, I believe the command
stream is now secure from having the client change it after submission,
however I'm not sure we are actually check the blit's are legal and not
doing anything...
I'll have to dig the datasheets out I suppose
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7790
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7861
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
Moin.
The
mach64-20060403-linux.i386
pacakge from FTP failed to compile with my 2.6.17-2 Debian kernel.
The error message boiled down to there's no 'count' in struct 'page'.
After changing
drm/linux-core/drm_compat.h:173
from
#define __put_page(p) atomic_dec((p)-count
Hi,
I have alwayls post this problem on dri-users.
I have Mach64 chipset and FC5; I compile the libdrm and module for
2.6.17-2187 kernel. I compiled only libdrm and drm module,
not Mesa.
Compilation finish succesfully, but when I restart xorg, I
have this error on the kernel output
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7790
[EMAIL PROTECTED] changed:
What|Removed |Added
On 10/22/06, Luca [EMAIL PROTECTED] wrote:
Hi, I have Mach64 chipset and FC5; I compile the libdrm and module for
2.6.17-2187 kernel. I compiled only libdrm and drm module,
not Mesa.
Compilation finish succesfully, but when I restart xorg, I
have this error on the kernel output
Component|General |Drivers/DRI/Mach64
Product|DRI |Mesa
Version|unspecified |CVS
--
Configure
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7790
--- Additional Comments From [EMAIL PROTECTED] 2006-10-20 15:44 ---
in understanding mach64 vertex setup but I don't think
it is clean enough to apply.
Possible outcomes of this bug report:
* mach64 has to be compiled with -fno-strict-aliasing to run ok. The culprit
for this is mach64FastRenderClippedPoly() in mach64_tris.c:1580. Either
drop the optimized version
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7861
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
---
(In reply to comment #41)
(In reply to comment #40)
With these changes can we finally turn on mach64 DRI support by default in
the
ati DDX?
I thought it was. I didn't need to do anything special to build it with DRI
support. I guess it was just never enabled on standard distros because
://bugs.freedesktop.org/attachment.cgi?id=7232action=view)
private DMA buffers / mach64-drm - try 4
This is that last one, please push this.
- drop an one-liner for a warning that was fixed otherwise (and the one-liner
would introduce the warning back)
- add an one-liner for a positive return
---
(In reply to comment #32)
I've gone over your latest patches. They look good to me. I applied them to my
local git trees and my Mesa working copy and tested them briefly on my amd64
with a PCI mach64. They seem to work nicely. I ran into some unrelated
problems
with the latest DRM that I want
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-10-02 07:43 ---
I
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-10-02 08:35 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-10-02 09:23 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-10-02 10:07 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6209
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
Bug 6242 depends on bug 6209, which changed state.
Bug 6209 Summary: [mach64] AGP
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
[EMAIL PROTECTED] changed:
What|Removed |Added
---
With these changes can we finally turn on mach64 DRI support by default in the
ati DDX?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug
---
(In reply to comment #40)
With these changes can we finally turn on mach64 DRI support by default in the
ati DDX?
I thought it was. I didn't need to do anything special to build it with DRI
support. I guess it was just never enabled on standard distros because the
default kernels didn't have a DRM
gone over your latest patches. They look good to me. I applied them to my
local git trees and my Mesa working copy and tested them briefly on my amd64
with a PCI mach64. They seem to work nicely. I ran into some unrelated problems
with the latest DRM that I want to get resolved first before pushing
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-09-26 07:14 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6209
--- Additional Comments From [EMAIL PROTECTED] 2006-09-25 13:05 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-09-25 13:06 ---
Any
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
[EMAIL PROTECTED] changed:
What|Removed |Added
up-to-date on current development
than I am, so feel free to beat me to it.
There are some changes that affect the shared DRM code (not mach64-specific). I
guess Dave Airlie should give his ok before this gets committed. Otherwise, last
time I reviewed this it looked pretty good and George
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6209
--- Additional Comments From [EMAIL PROTECTED] 2006-09-16 22:57 ---
Can
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7861
Summary: mach64 with render acceleration should restore texture
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7861
--- Additional Comments From [EMAIL PROTECTED] 2006-08-12 12:43 ---
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7790
Summary: Polygons incorrectly clipped by mach64 driver (ATI Rage
://bugs.freedesktop.org/attachment.cgi?id=6270action=view)
private DMA buffers / mach64-drm - try 3
- mach64_freelist_put moved to mach64_dma.c
- bump the driver date in mach64_drv.h
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
://bugs.freedesktop.org/attachment.cgi?id=6271action=view)
private DMA buffers / mach64-dri - try 2
Handle EAGAIN in mach64FireBlitLocked: call drmCommandWrite up to
MACH64_TIMEOUT times when EAGAIN is returned.
Also handle EAGAIN in mach64FlushVerticesLocked
the DRM_PCI_BUFFER_RO flag for linux. I'm not sure how many
people care about mach64 on BSD. I guess on BSD the flag would simply be
ignored, so PCI DMA buffers would still be mapped for writing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
://bugs.freedesktop.org/attachment.cgi?id=6235action=view)
private DMA buffers / mach64-ddx - try 2
Require a new mach64 DRM, also free the PCI DMA ring memory.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You
://bugs.freedesktop.org/attachment.cgi?id=6236action=view)
private DMA buffers / mach64-dri - try 1
Require new mach64 DRM.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because
://bugs.freedesktop.org/attachment.cgi?id=6241action=view)
private DMA buffers / mach64-ddx - try 3
stupid: check that PCI DMA ring was actually allocated before freeing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-06-22 08:47 ---
reviewing drm patches ;-)
Yep. I haven't forgotten about it yet.
I spent the last few evenings upgrading my home box to Dapper, so I have now
modular Xorg by default. I also installed a PCI Mach64 with 4MB Ram. I'll get
and build the relevant sources from GIT/CVS soon. I can't promise anything
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7260
Summary: mach64 texture memory mng cleanup
Product: Mesa
---
Created an attachment (id=5959)
-- (https://bugs.freedesktop.org/attachment.cgi?id=5959action=view)
use dri/common/texmem.c
This is my current diff. The current mach64 code is buggy, running a second DRI
client kills the first one. This patch fixes this by deletion. It removes ~480
LoC
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7127
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7127
Summary: mach64-20060403-linux.i386.tar.bz2 snapshot won't build
like to review your patches. Someone needs to kick my b*tt so I get a card
and try this stuff. I also got a private email from someone interested in
mach64. I suggested to try your patches. Give me a few weekends and don't forget
to remind me every once in a while
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6412
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-05-24 04:01 ---
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6412
[EMAIL PROTECTED] changed:
What|Removed |Added
://bugs.freedesktop.org/attachment.cgi?id=5283action=view)
private DMA buffers / mach64-ddx - try 1
Add DRM_PCI_READ_ONLY flag in drmBufDescFlags.
This flag has also to be added at
o libdrm/xf86drm.h
o xorg/hw/xfree86/os-support/xf86drm.h
--
Configure bugmail
://bugs.freedesktop.org/attachment.cgi?id=5284action=view)
private DMA buffers / mach64-drm - try 1
Add DRM_PCI_READ_ONLY flag in drmBufDescFlags.
When drm_mmap_dma sees this flag (set from drmAddBufs), it maps the PCI DMA
buffers as read-only (I just copied the code from drm_mmap).
An additional
Summary|[agp mach64] Use DMA buffers|[mach64] Use private DMA
|for mach64_dma_vertex |buffers (only)
--- Additional Comments From [EMAIL PROTECTED] 2006-04-12 10:44 ---
Start
|1
obsolete||
--- Additional Comments From [EMAIL PROTECTED] 2006-04-12 10:46 ---
Created an attachment (id=5269)
-- (https://bugs.freedesktop.org/attachment.cgi?id=5269action=view)
private DMA buffers / mach64-ddx
---
Created an attachment (id=5270)
-- (https://bugs.freedesktop.org/attachment.cgi?id=5270action=view)
private DMA buffers / mach64-dri
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because
---
Created an attachment (id=5271)
-- (https://bugs.freedesktop.org/attachment.cgi?id=5271action=view)
private DMA buffers / mach64-drm
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6242
--- Additional Comments From [EMAIL PROTECTED] 2006-04-10 11:34 ---
(In
that the first attribute is _TNL_ATTRIB_POS,
* at the same time, the mach64 native vertex format has the XYZW coords
* at non-consecutive positions spread inside the vertex.
*
* We reserve space for the XYZW coords with EMIT_PAD's and when the vertex
* is copied to the vertex buffer
1 - 100 of 1108 matches
Mail list logo
