VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2137 - 2139 of 16363)

Ticket Resolution Summary Owner Reporter
#10894 fixed glXBindTexImageEXT is not compliant -> fixed as of 1 Oct 2012 (4.2 and later) smspillaz
Description

glXBindTexImageEXT opens a new X connection on the first time it is invoked when the client may have a server grab. This is not compliant with the specification:

http://developer.download.nvidia.com/opengl/specs/GLX_EXT_texture_from_pixmap.txt

  1. Should users be required to re-bind the drawable to a texture after

the drawable has been rendered to?

It is difficult to define what the contents of the texture would be if we don't require this. Also, requiring this would allow implementations to perform an implicit copy at this point if they could not support texturing directly out of renderable memory.

The problem with defining the contents of the texture after rendering has occured to the associated drawable is that there is no way to synchronize the use of the buffer as a source and as a destination. Direct OpenGL rendering is not necessarily done in the same command stream as X rendering. At the time the pixmap is used as the source for a texturing operation, it could be in a state halfway through a copyarea operation in which half of it is say, white, and half is the result of the copyarea operation. How is this defined? Worse, some other OpenGL application could be halfway through a frame of rendering when the composite manager sources from it. The buffer might just contain the results of a "glClear" operation at that point.

To gurantee tear-free rendering, a composite manager would run as follows:

-receive request for compositing: XGrabServer() glXWaitX() or XSync() glXBindTexImageEXT()

<Do rendering/compositing>

glXReleaseTexImageEXT() XUngrabServer()

This results in a deadlock on startup with recent versions of compiz.

A patch to fix this is attached.

#11503 fixed glx.c in crOpenGL needs to open a second X Connection in order to process damage events -> fixed as of 21 Oct 2013, 4.2 and later smspillaz
Description

This is more of a follow up to https://www.virtualbox.org/ticket/10894 .

glx.c in crOpenGL still needs to open up a second X connection in order to process damage events. Processing damage on pixmaps before re-copying them is fine, but using a second X connection in order to fetch the damage is risky because at any point in your library, you could be affected by a server grab in the client process. There is a an issue with just listening for damage on the first connection, because the client might interfere with that. (I've found there are places where compiz may still hang in VirtualBox 4.2.6 because of this). So instead, the best way to handle it is to fetch damage synchronously from the server using XDamageSubtract and XFixesFetchRegion. This doesn't have any impact on performance, because the previous operation was already synchronous as we had to call XSync before fetching damage evnets.

I've attached a patch to do that. I've checked that it compiles, however I'm not able to get VirtualBox to install correctly, so I can't verify that it works as expected. However, I've written similar code in the past, so I'm 90% sure it should work.

(At the moment we're just working around this in compiz itself, but that's ugly because we had to do things like detect drivers).

#811 obsolete USB working incompletely (GSM tools) Smart
Description

I have many USB hardware for GSM programming like UFS, JAF boxes, smart-card readers etc.

All hardware can be detected on USB okay, but some hardware like smart-card readers working, but the most important UFS box is not. UFS' leds is blinking when it accessed, but then software prints "communication error". Nokia PC suite is not working too if the phone on USB. Some Siemens FFS-init software (working on PL-2303 usb-to-com cable) work but very unstable, can lose the phone half-programmed.

May be there is some timing-problems with USB... I don't know. Tell me if you need any logs or details.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy