[Bug 8554] using dri and dual head crashes x with i810 driver

2006-10-14 Thread bugzilla-daemon
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=8554  
 

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|General |Driver/i810
Product|DRI |xorg
Version|unspecified |7.1




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 00:59 ---
I think this is more correct as product  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8554] using dri and dual head crashes x with i810 driver

2006-10-14 Thread bugzilla-daemon
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=8554  
 

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|dri-|[EMAIL PROTECTED]
   |[EMAIL PROTECTED] |


  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)

2006-10-14 Thread Ryan Richter
I have a new Intel 965G board, and I'm trying to get DRI working.
Direct rendering is enabled, but all GL programs crash immediately.
The message 'DRM_I830_CMDBUFFER: -22' is printed on the tty, and the
kernel says:

[drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed

Additionally, glxinfo says (in addition to its normal output):

glxinfo: bufmgr_fake.c:1245: bmReleaseBuffers: Assertion `intel-locked' failed.

This is with 2.6.19-rc2 (and -rc1). Here's a .config and dmesg:

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.19-rc2
# Fri Oct 13 13:42:19 2006
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_ZONE_DMA32=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_CPUSETS is not set
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_STOP_MACHINE=y

#
# Block layer
#
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=anticipatory

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VSMP is not set
# CONFIG_MK8 is not set
CONFIG_MPSC=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_MICROCODE=y
CONFIG_MICROCODE_OLD_INTERFACE=y
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_X86_HT=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_SMP=y
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
# CONFIG_NUMA is not set
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_NR_CPUS=8
# CONFIG_HOTPLUG_CPU is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
# CONFIG_X86_MCE_AMD is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x20
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
# CONFIG_REORDER is not set
CONFIG_K8_NB=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y

#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER 

Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)

2006-10-14 Thread Keith Whitwell
Your drm module is out of date.

Keith

Ryan Richter wrote:
 I have a new Intel 965G board, and I'm trying to get DRI working.
 Direct rendering is enabled, but all GL programs crash immediately.
 The message 'DRM_I830_CMDBUFFER: -22' is printed on the tty, and the
 kernel says:
 
 [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed
 
 Additionally, glxinfo says (in addition to its normal output):
 
 glxinfo: bufmgr_fake.c:1245: bmReleaseBuffers: Assertion `intel-locked' 
 failed.
 
 This is with 2.6.19-rc2 (and -rc1). Here's a .config and dmesg:
 
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.19-rc2
 # Fri Oct 13 13:42:19 2006
 #
 CONFIG_X86_64=y
 CONFIG_64BIT=y
 CONFIG_X86=y
 CONFIG_ZONE_DMA32=y
 CONFIG_LOCKDEP_SUPPORT=y
 CONFIG_STACKTRACE_SUPPORT=y
 CONFIG_SEMAPHORE_SLEEPERS=y
 CONFIG_MMU=y
 CONFIG_RWSEM_GENERIC_SPINLOCK=y
 CONFIG_GENERIC_HWEIGHT=y
 CONFIG_GENERIC_CALIBRATE_DELAY=y
 CONFIG_X86_CMPXCHG=y
 CONFIG_EARLY_PRINTK=y
 CONFIG_GENERIC_ISA_DMA=y
 CONFIG_GENERIC_IOMAP=y
 CONFIG_ARCH_MAY_HAVE_PC_FDC=y
 CONFIG_ARCH_POPULATES_NODE_MAP=y
 CONFIG_DMI=y
 CONFIG_AUDIT_ARCH=y
 CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
 
 #
 # Code maturity level options
 #
 CONFIG_EXPERIMENTAL=y
 CONFIG_LOCK_KERNEL=y
 CONFIG_INIT_ENV_ARG_LIMIT=32
 
 #
 # General setup
 #
 CONFIG_LOCALVERSION=
 CONFIG_LOCALVERSION_AUTO=y
 CONFIG_SWAP=y
 CONFIG_SYSVIPC=y
 # CONFIG_IPC_NS is not set
 # CONFIG_POSIX_MQUEUE is not set
 # CONFIG_BSD_PROCESS_ACCT is not set
 # CONFIG_TASKSTATS is not set
 # CONFIG_UTS_NS is not set
 # CONFIG_AUDIT is not set
 # CONFIG_IKCONFIG is not set
 # CONFIG_CPUSETS is not set
 CONFIG_RELAY=y
 CONFIG_INITRAMFS_SOURCE=
 CONFIG_CC_OPTIMIZE_FOR_SIZE=y
 CONFIG_SYSCTL=y
 # CONFIG_EMBEDDED is not set
 CONFIG_UID16=y
 # CONFIG_SYSCTL_SYSCALL is not set
 CONFIG_KALLSYMS=y
 # CONFIG_KALLSYMS_ALL is not set
 # CONFIG_KALLSYMS_EXTRA_PASS is not set
 CONFIG_HOTPLUG=y
 CONFIG_PRINTK=y
 CONFIG_BUG=y
 CONFIG_ELF_CORE=y
 CONFIG_BASE_FULL=y
 CONFIG_FUTEX=y
 CONFIG_EPOLL=y
 CONFIG_SHMEM=y
 CONFIG_SLAB=y
 CONFIG_VM_EVENT_COUNTERS=y
 CONFIG_RT_MUTEXES=y
 # CONFIG_TINY_SHMEM is not set
 CONFIG_BASE_SMALL=0
 # CONFIG_SLOB is not set
 
 #
 # Loadable module support
 #
 CONFIG_MODULES=y
 CONFIG_MODULE_UNLOAD=y
 # CONFIG_MODULE_FORCE_UNLOAD is not set
 # CONFIG_MODVERSIONS is not set
 # CONFIG_MODULE_SRCVERSION_ALL is not set
 # CONFIG_KMOD is not set
 CONFIG_STOP_MACHINE=y
 
 #
 # Block layer
 #
 CONFIG_BLOCK=y
 CONFIG_LBD=y
 # CONFIG_BLK_DEV_IO_TRACE is not set
 # CONFIG_LSF is not set
 
 #
 # IO Schedulers
 #
 CONFIG_IOSCHED_NOOP=y
 CONFIG_IOSCHED_AS=y
 CONFIG_IOSCHED_DEADLINE=y
 CONFIG_IOSCHED_CFQ=y
 CONFIG_DEFAULT_AS=y
 # CONFIG_DEFAULT_DEADLINE is not set
 # CONFIG_DEFAULT_CFQ is not set
 # CONFIG_DEFAULT_NOOP is not set
 CONFIG_DEFAULT_IOSCHED=anticipatory
 
 #
 # Processor type and features
 #
 CONFIG_X86_PC=y
 # CONFIG_X86_VSMP is not set
 # CONFIG_MK8 is not set
 CONFIG_MPSC=y
 # CONFIG_GENERIC_CPU is not set
 CONFIG_X86_L1_CACHE_BYTES=128
 CONFIG_X86_L1_CACHE_SHIFT=7
 CONFIG_X86_INTERNODE_CACHE_BYTES=128
 CONFIG_X86_TSC=y
 CONFIG_X86_GOOD_APIC=y
 CONFIG_MICROCODE=y
 CONFIG_MICROCODE_OLD_INTERFACE=y
 # CONFIG_X86_MSR is not set
 # CONFIG_X86_CPUID is not set
 CONFIG_X86_HT=y
 CONFIG_X86_IO_APIC=y
 CONFIG_X86_LOCAL_APIC=y
 CONFIG_MTRR=y
 CONFIG_SMP=y
 # CONFIG_SCHED_SMT is not set
 CONFIG_SCHED_MC=y
 CONFIG_PREEMPT_NONE=y
 # CONFIG_PREEMPT_VOLUNTARY is not set
 # CONFIG_PREEMPT is not set
 CONFIG_PREEMPT_BKL=y
 # CONFIG_NUMA is not set
 CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_ARCH_FLATMEM_ENABLE=y
 CONFIG_SELECT_MEMORY_MODEL=y
 CONFIG_FLATMEM_MANUAL=y
 # CONFIG_DISCONTIGMEM_MANUAL is not set
 # CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 # CONFIG_SPARSEMEM_STATIC is not set
 CONFIG_SPLIT_PTLOCK_CPUS=4
 CONFIG_RESOURCES_64BIT=y
 CONFIG_NR_CPUS=8
 # CONFIG_HOTPLUG_CPU is not set
 CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
 CONFIG_HPET_TIMER=y
 CONFIG_HPET_EMULATE_RTC=y
 CONFIG_IOMMU=y
 # CONFIG_CALGARY_IOMMU is not set
 CONFIG_SWIOTLB=y
 CONFIG_X86_MCE=y
 CONFIG_X86_MCE_INTEL=y
 # CONFIG_X86_MCE_AMD is not set
 # CONFIG_KEXEC is not set
 # CONFIG_CRASH_DUMP is not set
 CONFIG_PHYSICAL_START=0x20
 CONFIG_SECCOMP=y
 # CONFIG_CC_STACKPROTECTOR is not set
 # CONFIG_HZ_100 is not set
 # CONFIG_HZ_250 is not set
 CONFIG_HZ_1000=y
 CONFIG_HZ=1000
 # CONFIG_REORDER is not set
 CONFIG_K8_NB=y
 CONFIG_GENERIC_HARDIRQS=y
 CONFIG_GENERIC_IRQ_PROBE=y
 CONFIG_ISA_DMA_API=y
 CONFIG_GENERIC_PENDING_IRQ=y
 
 #
 # Power management options
 #
 CONFIG_PM=y
 CONFIG_PM_LEGACY=y
 # CONFIG_PM_DEBUG is not set
 # CONFIG_PM_SYSFS_DEPRECATED is not set
 
 #
 # ACPI (Advanced Configuration and Power Interface) Support
 #
 CONFIG_ACPI=y
 # CONFIG_ACPI_AC is not set
 # CONFIG_ACPI_BATTERY is not set
 CONFIG_ACPI_BUTTON=y
 CONFIG_ACPI_VIDEO=y
 # CONFIG_ACPI_HOTKEY is not set
 CONFIG_ACPI_FAN=y
 # CONFIG_ACPI_DOCK is not set
 CONFIG_ACPI_PROCESSOR=y
 

Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)

2006-10-14 Thread Keith Whitwell
Arjan van de Ven wrote:
 On Sat, 2006-10-14 at 09:55 +0100, Keith Whitwell wrote:
 Your drm module is out of date.
 
 
 Since the reporter is using the latest brand spanking new kernel, that
 is highly unlikely unless something else in the software universe is
 assuming newer-than-brand-spanking-new.

Heh.  I missed that in the title line.  I'll retire quietly...

Keith


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 4707] r200 driver should support ARB_point_parameters

2006-10-14 Thread bugzilla-daemon
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=4707  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 03:05 ---
The potential hitch is that you need to make sure this test is reevaluated for
all primitives drawn.  Typically the drivers look at the Mesa state and set
hardware state appropriately and then try to avoid re-checking again and again
unless there are actual Mesa statechanges.  Unfortunately you now need to do
that because you are basing hardware state off not just Mesa state but what
primitives are coming down the pipe, which Mesa doesn't (yet) consider a
statechange.

At a certain level, if the app requests this state, its' fair enough that it
pays for computing the values.  Unless you find a real instance where this is a
problem - ie an app that asks for this state and then doesn't render points
*and* becomes noticably slower as a result, I would consider it not worth
optimizing for.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8250] Warcraft player avatars not rendered correctly when GL_ARB_vertex_program enabled.

2006-10-14 Thread bugzilla-daemon
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=8250  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 06:07 ---
I'm disabling GL_ARB_vertex_program via Wine, which has a registry key for
listing OpenGL extensions that you don't want to be used:

http://appdb.winehq.org/appimage.php?iId=3746  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Texture function opengl specification

2006-10-14 Thread Jerome Glisse

Hi,

I am wondering if i am fully understanding how texture value
should be computed. I am refering here to section 3.8.13
of opengl specification and specialy to table 3.21.

My understanding is that when you got an RGB texture the
As = 1 but when computing you use Ap which equal to the
primary color component of incoming fragment if you are
texture 0, or to the previous A value if you are texture  0
ie if you are texture 1 you use A from texture 0, if you are
texture 2 you use A from texture 1 right ?

According to fragment program extension, TEX, TXP, ... should
give you the right A value (Ap depending on which texture unit
you are using). I got the feeling that r300/r400 hardware doesn't
follow this. At least fglrx driver (one packaged in ubuntu edgy)
fail at pixel format test using TEX instruction. I also attach a
small app which should test that. If you launch it res should
be (255, 0, 0, 0) but i will be (255, 0, 0, 255). If anyone could
test that on a windows with r300 hardware.

I may also don't fully understand this part of the specification :)
Btw the Ap value seems a bit hard things to follow i guess that
ATI might have choose to save some silicon and simplify design
than to conform to this specification.

best,
Jerome Glisse
#include assert.h
#include stdio.h
#include stdlib.h
#include string.h
#define GL_GLEXT_PROTOTYPES
#include GL/glut.h

#define W 64
#define H 64

static GLubyte my_image[W*H*4];
static GLuint alphaBits;

#define USE_FRAG_PROG 1

void makeCheckImages(void)
{
	int i, j, c;
   
	for (i = 0; i  H; i++) {
		for (j = 0; j  W; j++) {
			c = i0x8)==0)^((j0x8)==0)))*255;
			c = 255;
			my_image[j * 4 + i * W * 4 + 0] = (GLubyte) c;
			my_image[j * 4 + i * W * 4 + 1] = (GLubyte) 0;
			my_image[j * 4 + i * W * 4 + 2] = (GLubyte) 0;
			my_image[j * 4 + i * W * 4 + 3] = (GLubyte) 0;
		}
	}
}

void init(void)
{
	glGetIntegerv(GL_ALPHA_BITS, alphaBits);
	printf(GL_ALPHA_BITS: %d\n, alphaBits);

	glDrawBuffer(GL_FRONT);
	glReadBuffer(GL_FRONT);
	glClearColor(0.0, 0.0, 0.0, 0.0);

	makeCheckImages();

	glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST);
	glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST);
	glTexEnvi(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE, GL_REPLACE);
	glTexImage2D(GL_TEXTURE_2D, 0, GL_RGB, W, H, 0,
		 GL_RGBA, GL_UNSIGNED_BYTE, my_image);

#if USE_FRAG_PROG
	{
		GLuint prog;
		static const char *progText =
			!!ARBfp1.0\n
			TEX result.color, fragment.texcoord[0], 
			texture[0], 2D; \n
			END \n
			;

		if (!glutExtensionSupported(GL_ARB_fragment_program)) {
			printf(Error: GL_ARB_fragment_program 
			   not supported!\n);
			exit(1);
		}

		glGenProgramsARB(1, prog);
		glBindProgramARB(GL_FRAGMENT_PROGRAM_ARB, prog);
		glProgramStringARB(GL_FRAGMENT_PROGRAM_ARB,
   GL_PROGRAM_FORMAT_ASCII_ARB,
   strlen(progText),
   (const GLubyte *) progText);
		if (glGetError()) {
			fprintf(stderr, Bad fragment program, error: %s\n,
glGetString(GL_PROGRAM_ERROR_STRING_ARB));
			exit(0);
		}
	}
#endif
}

void display(void)
{
	GLubyte *res = (GLubyte *)malloc(W * H * 4);	

	glClear(GL_COLOR_BUFFER_BIT);

	glViewport(0, 0, W, H);

	glColor4f(0.0, 0.0, 0.0, 0.0);
	glEnable(GL_TEXTURE_2D);

#if USE_FRAG_PROG
	glEnable(GL_FRAGMENT_PROGRAM_ARB);
#endif

	glBegin(GL_QUADS);
	glTexCoord2f(0.0, 0.0);  glVertex2f(-1.0, -1.0);
	glTexCoord2f(1.0, 0.0);  glVertex2f( 1.0, -1.0);
	glTexCoord2f(1.0, 1.0);  glVertex2f( 1.0,  1.0);
	glTexCoord2f(0.0, 1.0);  glVertex2f(-1.0,  1.0);
	glEnd();

#if USE_FRAG_PROG
	glDisable(GL_FRAGMENT_PROGRAM_ARB);
#endif

	glDisable(GL_TEXTURE_2D);

	glFlush();
//	glutSwapBuffers();

	glReadPixels(0, 0, W, H, GL_RGBA, GL_UNSIGNED_BYTE, res);

	printf(pixel(0,0)=(%d, %d, %d, %d)\n,
	   my_image[0],my_image[1],
	   my_image[2],my_image[3]);
	printf(-res(0,0)=(%d, %d, %d, %d)\n,
	   res[0],res[1],
	   res[2],res[3]);

	free(res);
}

void reshape(int w, int h)
{
	glLoadIdentity();
}

void keyboard(unsigned char key, int x, int y)
{
	switch ( key ) {
	case 27:
		exit(0);
		break;
	default:
		break;
	}
}

void idle(void)
{
//	glutPostRedisplay();
}

int main(int argc, char** argv)
{
	glutInit(argc, argv);
	glutInitDisplayMode(GLUT_RGBA);
	glutInitWindowSize(W, H);
	glutCreateWindow(BUG 7235);

	init();

	glutDisplayFunc(display);
	glutReshapeFunc(reshape);
	glutKeyboardFunc(keyboard);
	glutIdleFunc(idle);
	glutMainLoop();
	return 0;
}
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Help needed! I don't understand the DRM linux GART code.

2006-10-14 Thread Christian Neumair
Dear DRI/DRM developers,

I'm trying to understand the DRM GART interaction with the linux DRM
core, because I'm trying to run the M300 Mobility (PCI Express) with
Xegl to help out with development. I fetched MESA and DRM, built them
(after applying some fixes), and built Xegl.

I'm now trying to run Xegl with a frame buffer, and when starting get

[17182196.816000] [drm:radeon_do_init_cp]
[17182196.816000] [drm:radeon_do_init_cp] dev_priv-cp_ring-handle
e1ca2000
[17182196.816000] [drm:radeon_do_init_cp] dev_priv-ring_rptr-handle
e1da3000
[17182196.816000] [drm:radeon_do_init_cp] dev-agp_buffer_map-handle
e1da4000
[17182196.816000] [drm] Setting GART location based on old memory map
[17182196.816000] [drm:radeon_do_init_cp] dev_priv-gart_size 8388608
[17182196.816000] [drm:radeon_do_init_cp] dev_priv-gart_vm_start
0x400
[17182196.816000] [drm:radeon_do_init_cp] dev_priv-gart_buffers_offset
0x4102000
[17182196.816000] [drm:radeon_do_init_cp] Setting phys_pci_gart to
 07FF8000
[17182196.816000] [drm:drm_ati_pcigart_init] PCI: Gart Table: VRAM
07FF8000 mapped at 
[17182196.816000] BUG: unable to handle kernel NULL pointer dereference
at virtual address 
(...)

Because the driver is said to not work on PCI express cards, I already
expected something like this, but I wasn't able to fix it up to now.
My problem is that I read various GART interaction code having different
code paths depending on whether 

a) the built-in card is AGP, PCIE or PCI
b) the GART table is stored in FB or in MAIN memory

I'm specifically puzzled by code relating to b), there is a lot of
offset juggling, for instance in radeon_cp.c:radeon_do_init_cp, where
for PCI cards the (otherwised unused/0-initialized) mapping.handle is
under some circumstances assigned to dev_priv-gart_info.addr, which is
then passed to drm_ati_pcigart_init.

This code in turn will not malloc the PCIGART table for FB mapping
tables, and thus dereference a NULL pointer when trying to memset the 0
address.

My problem is now that while I found many articles describing the
general idea of DRI and DRM, I could not found papers on the interaction
with GART, and the concrete implementation design choices. I don't
understand the role of the various offsets, including the fb_offset,
radeon_fb_delta and gart_vm_start. An image containing some suggestive
base pointer addressing illustrations on what memory areas are used, and
where they are located would help me a lot.

Maybe I'm just to dumb to grasp more than the big picture, and the code
comments should be sufficient, or maybe I missed any docs?

-- 
Christian Neumair [EMAIL PROTECTED]


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)

2006-10-14 Thread Avi Kivity
Ryan Richter wrote:

 I have a new Intel 965G board, and I'm trying to get DRI working.
 Direct rendering is enabled, but all GL programs crash immediately.
 The message 'DRM_I830_CMDBUFFER: -22' is printed on the tty, and the
 kernel says:

 [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed


I had the same problem.  Recompiling i965_dri.so in order to insert 
debugging code fixed it for me.  It continued working  after a mesa 
package update so I assumed it was a miscompilation.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


DPMS on i815 over DVI

2006-10-14 Thread Jan Dittmer
Hi All,

is there any progress regarding bugzilla 4229? It's a bit of a pain
to remember to turn the lcd off.
Is this a problem of missing documentation or missing time on your side?
Anything I can do to help resolve this issue?

Thanks,

Jan

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock

2006-10-14 Thread bugzilla-daemon
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=7111  
 

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 09:55 ---
I can confirm this: With correct permissions to /dev/dri/card0, the X server 
freezes but the mouse is still moving, and the locking message is written to 
the logfile.

When I change these permissions, it freezes too, but the locking message is 
not written. I see that the intro of racer still runs fast enough (maybe 
because of AIGLX).

Now the interesting part: I have a Mobility Radeon 9600, so I use the 
experimental r300 driver. If I start racer with the environment variable 
R300_SPAN_DISABLE_LOCKING set to 1, it runs fine.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock

2006-10-14 Thread bugzilla-daemon
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=7111  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 10:16 ---
(In reply to comment #5)
 Now the interesting part: I have a Mobility Radeon 9600, so I use the 
 experimental r300 driver. If I start racer with the environment variable 
 R300_SPAN_DISABLE_LOCKING set to 1, it runs fine.

This indicates the problem being due to a crash in a software fallback or
similar. If that's the case, killing the application should allow the X server
to continue normally, and you should try and get a backtrace of the crash (from
a remote login).  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock

2006-10-14 Thread bugzilla-daemon
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=7111  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 10:50 ---
After killing racer.bin, the system continues to run normally.

I'll try to get a backtrace in a few days. How exactly do I do that? Is it ok 
to kill the X-Server with SIGSEGV or SIGABRT? Or do I have to use the debugger 
gdb?

Besides, wouldn't this be better assigned to the mesa-dev 
(mesa3d-dev@lists.sourceforge.net) mailing list?  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)

2006-10-14 Thread Keith Packard
On Fri, 2006-10-13 at 15:45 -0400, Ryan Richter wrote:
 I have a new Intel 965G board, and I'm trying to get DRI working.
 Direct rendering is enabled, but all GL programs crash immediately.
 The message 'DRM_I830_CMDBUFFER: -22' is printed on the tty, and the
 kernel says:
 
 [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed

The 915 DRM validates commands sent to the card from the application to
ensure they aren't directing the card to access memory outside of the
graphics area. At present the module validates only 915/945 commands
correctly and the 965 uses slightly different commands. I haven't walked
over the entire GL library, but it seems possible that this error is
being caused by the mis-validation of the command stream. We need to
update the DRM driver to reflect the new commands, but in the meanwhile,
you might try disabling the validation in the kernel (which will expose
your system to a local root compromise) and seeing if that doesn't
eliminate this message.

-- 
[EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8645] New: Issue when rendering with 2 contexts to one window

2006-10-14 Thread bugzilla-daemon
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=8645  
 
   Summary: Issue when rendering with 2 contexts to one window
   Product: DRI
   Version: XOrg CVS
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: General
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]


r200 dri seems to have some issues when an application renders from 2 threads 
to the same window with 2 different contexts.

According to the glXSwapBuffers manpage it is ok to render to one window with 
2 contexts. I have experienced issues with the glDrawBuffer setting when doing 
that. I will attach a small test application which shows the bug.

(sorry if this bug report appeared 2 times - I had a system crash when I filed 
it the first time, I couldn't find the bug, so I assumed it wasn't filed and 
rewrote it)  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8645] Issue when rendering with 2 contexts to one window

2006-10-14 Thread bugzilla-daemon
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=8645  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 12:34 ---
Created an attachment (id=7414)
 -- (https://bugs.freedesktop.org/attachment.cgi?id=7414action=view)
Test app to show the bug

This app creates a window and two glx contexts and starts 2 threads which use
the contexts to render to the window. The threads are only hackily
synchronised, but it should work, to my knowledge.

The program should draw a blue quad and a red primitive, with the red primitive
beeing partially covered by the quad. The problem is that the quad flickers as
if it was drawn to the front buffer. The flickering goes away if I move the
glDrawBuffers(GL_BACK); statements into the rendering loop in both threads.

The depth buffer seems to be shared properly between the contexts, and the
glColor state seems to work too.

The background is implementing multithreaded Direct3D for Wine. Direct3D
applications can do rendering from any thread, while a gl context is only valid
for one thread. Because of that a d3d app using differnt threads will just
crash with the current wine code.

We can't easilly take away the context from the thread it is assigned to
because we have no control over the threads, so we hope to be able to create
one context for each thread that does the rendering and share textures, VBOs,
shaders, ..., between the contexts and to render to the same window. Locking in
the d3d libs will make sure that only one thread renders at the same time.
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8645] Issue when rendering with 2 contexts to one window

2006-10-14 Thread bugzilla-daemon
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=8645  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 12:37 ---
Sorry, I forgot to mention, the version identification from glxinfo is:

OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 20060602 AGP 4x x86/MMX/SSE2 TCL
OpenGL version string: 1.3 Mesa 6.5.1
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Texture function opengl specification

2006-10-14 Thread Roland Scheidegger
Jerome Glisse wrote:
 Hi,
 
 I am wondering if i am fully understanding how texture value should 
 be computed. I am refering here to section 3.8.13 of opengl 
 specification and specialy to table 3.21.
 
 My understanding is that when you got an RGB texture the As = 1 but 
 when computing you use Ap which equal to the primary color component 
 of incoming fragment if you are texture 0, or to the previous A value
  if you are texture  0 ie if you are texture 1 you use A from
 texture 0, if you are texture 2 you use A from texture 1 right ?
yes, though not A from texture 0/1 but A from texture environment
0/1. However, this is only true if you use the fixed texture
environment modes, this has no relevance if you use combine mode, where
you specify all args directly. So at least for the combine mode, it is
really necessary that As is indeed 1 for RGB textures.

 According to fragment program extension, TEX, TXP, ... should give 
 you the right A value (Ap depending on which texture unit you are 
 using).
That's not how I read that. TEX,TXP,... refer to texture sampling only,
there is no thing as previous unit there. Thus, for an RGB texture, A
should be always 1.

 I got the feeling that r300/r400 hardware doesn't follow this.
Well, apparently r300 should not only support swizzling, but also
replacing some args with 1 or 0. For the case of RGB888 textures, those
aren't supported anyway, so there is absolutely no difference to a
RGBA texture for the hw - the mesa texstore function should fill in
the 1's.

 At least fglrx driver (one packaged in ubuntu edgy) fail at pixel
 format test using TEX instruction. I also attach a small app which
 should test that. If you launch it res should be (255, 0, 0, 0) but i
 will be (255, 0, 0, 255). If anyone could test that on a windows with
 r300 hardware.
Maybe the test could be broken? I think at least for your app,
(255,0,0,255) is the right answer. If you'd not use frag progs but 
instead of GL_REPLACE a tex combine function you'd get the same.

 I may also don't fully understand this part of the specification :) 
 Btw the Ap value seems a bit hard things to follow i guess that ATI 
 might have choose to save some silicon and simplify design than to 
 conform to this specification.
As said, I don't think that previous environment needs to be tracked. 
table 3.21 defines how the component mapping works, and the rest is left 
up to the fragment program without the opengl implementation trying to 
change the meaning of the arguments depending on what type of texture is 
bound.

Roland

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Texture function opengl specification

2006-10-14 Thread Jerome Glisse
On 10/14/06, Roland Scheidegger [EMAIL PROTECTED] wrote:
 Jerome Glisse wrote:
  Hi,
 
  I am wondering if i am fully understanding how texture value should
  be computed. I am refering here to section 3.8.13 of opengl
  specification and specialy to table 3.21.
 
  My understanding is that when you got an RGB texture the As = 1 but
  when computing you use Ap which equal to the primary color component
  of incoming fragment if you are texture 0, or to the previous A value
   if you are texture  0 ie if you are texture 1 you use A from
  texture 0, if you are texture 2 you use A from texture 1 right ?
 yes, though not A from texture 0/1 but A from texture environment
 0/1. However, this is only true if you use the fixed texture
 environment modes, this has no relevance if you use combine mode, where
 you specify all args directly. So at least for the combine mode, it is
 really necessary that As is indeed 1 for RGB textures.

I guess i still don't fully get all the subtle difference that happen when
you are in fixed pipeline or in vp/fp one. I will study this again :).

  According to fragment program extension, TEX, TXP, ... should give
  you the right A value (Ap depending on which texture unit you are
  using).
 That's not how I read that. TEX,TXP,... refer to texture sampling only,
 there is no thing as previous unit there. Thus, for an RGB texture, A
 should be always 1.

What induced me to this , is that in fragment program extension
description they say to look at table 3.21 and in this one there is
reference to Ap for A in RGB. Anyway i think you are right here.

  I got the feeling that r300/r400 hardware doesn't follow this.
 Well, apparently r300 should not only support swizzling, but also
 replacing some args with 1 or 0. For the case of RGB888 textures, those
 aren't supported anyway, so there is absolutely no difference to a
 RGBA texture for the hw - the mesa texstore function should fill in
 the 1's.

  At least fglrx driver (one packaged in ubuntu edgy) fail at pixel
  format test using TEX instruction. I also attach a small app which
  should test that. If you launch it res should be (255, 0, 0, 0) but i
  will be (255, 0, 0, 255). If anyone could test that on a windows with
  r300 hardware.
 Maybe the test could be broken? I think at least for your app,
 (255,0,0,255) is the right answer. If you'd not use frag progs but
 instead of GL_REPLACE a tex combine function you'd get the same.

  I may also don't fully understand this part of the specification :)
  Btw the Ap value seems a bit hard things to follow i guess that ATI
  might have choose to save some silicon and simplify design than to
  conform to this specification.
 As said, I don't think that previous environment needs to be tracked.
 table 3.21 defines how the component mapping works, and the rest is left
 up to the fragment program without the opengl implementation trying to
 change the meaning of the arguments depending on what type of texture is
 bound.

 Roland


Thx for helping me on that, i was a bit confuse on how all this should work.

Jerome Glisse

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 4707] r200 driver should support ARB_point_parameters

2006-10-14 Thread bugzilla-daemon
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=4707  
 

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 17:24 ---
(In reply to comment #5)
 At a certain level, if the app requests this state, its' fair enough that it
 pays for computing the values.  Unless you find a real instance where this is 
 a
 problem - ie an app that asks for this state and then doesn't render points
 *and* becomes noticably slower as a result, I would consider it not worth
 optimizing for.
Fair enough. The theoretical maximum performance hit would probably be 25%
(which is the vertex size increase caused by submitting point size since the
minimum otherwise is 3 floats for position and 1 float (4UB) for color0, I'd
think the point size calculation itself shouldn't be that expensive), though I'd
think in practice it should well stay below that.
And the additional tests needed in tcl mode for ARB_point_sprite (to disable
perspective correction) didn't seem to have a visible performance impact
neither, though I wondered if it's the reason ati does not support that
extension on r200 with any of its drivers (even those for other operating 
systems).  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8645] Issue when rendering with 2 contexts to one window

2006-10-14 Thread bugzilla-daemon
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=8645  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-10-14 18:08 ---
Have you enabled pageflip? It seems to work just fine here without pageflip, but
not with pageflip enabled.
I think the issue here is that in all of the radeon drivers (didn't look at
others), the radeon/r200PageFlip function which will finally get called upon a
glxSwapBuffers call updates the (per-context) hw state to adjust for the new
offsets. But since the drawable ultimately is bound to 2 contexts the other one
will still use the old values.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel