Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update cl_arm_import_memory specification #130

Merged
merged 1 commit into from
Sep 29, 2022
Merged

Update cl_arm_import_memory specification #130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions extensions/arm/cl_arm_import_memory.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ IP Status

Version

Revision: #11, Feb 15th, 2021
Revision: #12, Sep 29th, 2022

Number

Expand Down Expand Up @@ -178,9 +178,9 @@ New Procedures and Functions
_not_ include cases where physical pages are not allocated. For specific
behaviour see documentation for those memory types.

CL_INVALID_OPERATION when an imported memory object has been passed to
one of the following API functions (they can't be used with imported
memory objects):
Prior to version 1.1.0, CL_INVALID_OPERATION when an imported memory
object has been passed to one of the following API functions (they can't
be used with imported memory objects):

* clEnqueueMapBuffer
* clEnqueueMapImage
Expand Down Expand Up @@ -452,3 +452,6 @@ Revision History
Revision: #10, Feb 13th, 2020 - Make dma_buf <-> host data consistency optional.
Revision: #11, Feb 15th, 2021 - Add support for Android hardware buffer
plane/layer selection.
Revision: #12, Sep 29th, 2022 - Version 1.1.0 of cl_arm_import_memory adds
support for host access to imported
memory for all memory types.