Displaying 14 results from an estimated 14 matches for "openml".
Did you mean:
openmp
2001 Apr 14
1
OpenML, Khronos, and dmSDK
It looks like SGI has an open source project called dmSDK (digital media
SDK) that is similar in some ways to the goals of the Xiph.org projects.
Apparently it's the basis for OpenML, which is run by the Khronos SIG,
which looks like a consortium made up of various companies like S3, SGI,
and Intel.
You can find more about dmSDK at http://oss.sgi.com
and more about OpenML and Khronos SIG at http://www.khronos.org
I'm surprised that no one's found these before I did t...
2001 Apr 14
0
OpenML, Khronos, and dmSDK (UU2536490)
** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL **
** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO **
** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. **
Dear Customer,
We have received your message ("Re: [vorbis] OpenML, Khronos, and
dmSDK") and forwarded it to the appropriate personnel for processing.
To help us provide you with the best possible service, please refer to
trouble ticket number UU2536490 somewhere in all correspondence (or if
you should call Customer Support) regarding this matter. For your...
2020 Jan 12
2
[PATCH 23/23] drm: Cleanup VBLANK callbacks in struct drm_driver
...e immediately after end of the VBLANK interval. If the
> - * @crtc is currently inside VBLANK, this will be a time in the future.
> - * If the @crtc is currently scanning out a frame, this will be the
> - * past start time of the current scanout. This is meant to adhere
> - * to the OpenML OML_sync_control extension specification.
> - *
> - * Paramters:
> - *
> - * dev:
> - * dev DRM device handle.
> - * pipe:
> - * crtc for which timestamp should be returned.
> - * max_error:
> - * Maximum allowable timestamp error in nanoseconds.
>...
2020 Jan 10
0
[PATCH 23/23] drm: Cleanup VBLANK callbacks in struct drm_driver
...ng out,
- * the time immediately after end of the VBLANK interval. If the
- * @crtc is currently inside VBLANK, this will be a time in the future.
- * If the @crtc is currently scanning out a frame, this will be the
- * past start time of the current scanout. This is meant to adhere
- * to the OpenML OML_sync_control extension specification.
- *
- * Paramters:
- *
- * dev:
- * dev DRM device handle.
- * pipe:
- * crtc for which timestamp should be returned.
- * max_error:
- * Maximum allowable timestamp error in nanoseconds.
- * Implementation should strive to provide...
2020 Jan 20
0
[PATCH v3 03/22] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...ng out,
+ * the time immediately after end of the vblank interval. If the
+ * @crtc is currently inside vblank, this will be a time in the future.
+ * If the @crtc is currently scanning out a frame, this will be the
+ * past start time of the current scanout. This is meant to adhere
+ * to the OpenML OML_sync_control extension specification.
+ *
+ * Parameters:
+ *
+ * crtc:
+ * CRTC for which timestamp should be returned.
+ * max_error:
+ * Maximum allowable timestamp error in nanoseconds.
+ * Implementation should strive to provide timestamp
+ * with an error of at mo...
2020 Jan 20
0
[Intel-gfx] [PATCH v3 03/22] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...e immediately after end of the vblank interval. If the
> + * @crtc is currently inside vblank, this will be a time in the future.
> + * If the @crtc is currently scanning out a frame, this will be the
> + * past start time of the current scanout. This is meant to adhere
> + * to the OpenML OML_sync_control extension specification.
> + *
> + * Parameters:
> + *
> + * crtc:
> + * CRTC for which timestamp should be returned.
> + * max_error:
> + * Maximum allowable timestamp error in nanoseconds.
> + * Implementation should strive to provide t...
2020 Jan 15
0
[PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...ng out,
+ * the time immediately after end of the vblank interval. If the
+ * @crtc is currently inside vblank, this will be a time in the future.
+ * If the @crtc is currently scanning out a frame, this will be the
+ * past start time of the current scanout. This is meant to adhere
+ * to the OpenML OML_sync_control extension specification.
+ *
+ * Parameters:
+ *
+ * crtc:
+ * CRTC for which timestamp should be returned.
+ * max_error:
+ * Maximum allowable timestamp error in nanoseconds.
+ * Implementation should strive to provide timestamp
+ * with an error of at mo...
2020 Jan 15
2
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...e immediately after end of the vblank interval. If the
> + * @crtc is currently inside vblank, this will be a time in the future.
> + * If the @crtc is currently scanning out a frame, this will be the
> + * past start time of the current scanout. This is meant to adhere
> + * to the OpenML OML_sync_control extension specification.
> + *
> + * Parameters:
> + *
> + * crtc:
> + * CRTC for which timestamp should be returned.
> + * max_error:
> + * Maximum allowable timestamp error in nanoseconds.
> + * Implementation should strive to provide t...
2020 Jan 16
0
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...ter end of the vblank interval. If the
>> + * @crtc is currently inside vblank, this will be a time in the future.
>> + * If the @crtc is currently scanning out a frame, this will be the
>> + * past start time of the current scanout. This is meant to adhere
>> + * to the OpenML OML_sync_control extension specification.
>> + *
>> + * Parameters:
>> + *
>> + * crtc:
>> + * CRTC for which timestamp should be returned.
>> + * max_error:
>> + * Maximum allowable timestamp error in nanoseconds.
>> + * Implement...
2020 Jan 10
36
[PATCH 00/23] drm: Clean up VBLANK callbacks in struct drm_driver
VBLANK handlers in struct drm_driver are deprecated. Only legacy,
non-KMS drivers are supposed to used them. DRM drivers with kernel
modesetting are supposed to use VBLANK callbacks of the CRTC
infrastructure.
This patchset converts all DRM drivers to CRTC VBLANK callbacks and
cleans up struct drm_driver. The remaining VBLANK callbacks in struct
drm_driver are only used by legacy drivers.
2020 Jan 20
26
[PATCH v3 00/22] drm: Clean up VBLANK callbacks in struct drm_driver
VBLANK handlers in struct drm_driver are deprecated. Only legacy,
non-KMS drivers are supposed to used them. DRM drivers with kernel
modesetting are supposed to use VBLANK callbacks of the CRTC
infrastructure.
This patchset converts all DRM drivers to CRTC VBLANK callbacks and
cleans up struct drm_driver. The remaining VBLANK callbacks in struct
drm_driver are only used by legacy drivers.
Patch
2012 Feb 15
11
[Patches][nouveau/ddx]: Improvements to bufferswap implementation and timestamping
Hi,
here a set of patches against the nouveau-ddx. This is an extended and
revised set, based on Francisco Jerez feedback from autumn last year.
[1/9] Makes pageflipping work again on X-Server 1.12rc. It apparently stopped
working somewhere around Xorg 1.11+.
[2/9] Implements handling of pageflip completion events from the kernel.
Francisco Jerez argument against including it was that the
2020 Jan 15
26
[PATCH v2 00/21] drm: Clean up VBLANK callbacks in struct drm_driver
VBLANK handlers in struct drm_driver are deprecated. Only legacy,
non-KMS drivers are supposed to used them. DRM drivers with kernel
modesetting are supposed to use VBLANK callbacks of the CRTC
infrastructure.
This patchset converts all DRM drivers to CRTC VBLANK callbacks and
cleans up struct drm_driver. The remaining VBLANK callbacks in struct
drm_driver are only used by legacy drivers.
2020 Jan 23
30
[PATCH v4 00/22] drm: Clean up VBLANK callbacks in struct drm_driver
VBLANK handlers in struct drm_driver are deprecated. Only legacy,
non-KMS drivers are supposed to used them. DRM drivers with kernel
modesetting are supposed to use VBLANK callbacks of the CRTC
infrastructure.
This patchset converts all DRM drivers to CRTC VBLANK callbacks and
cleans up struct drm_driver. The remaining VBLANK callbacks in struct
drm_driver are only used by legacy drivers.
Patch