| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes are the necessary complement to corresponding
mesa commit 5981ab5 "gallium: remove PIPE_BIND_TRANSFER_READ/WRITE"
Fixes the following building errors:
external/drm_gralloc/gralloc_drm_pipe.c:102:11: error: use of undeclared identifier 'PIPE_BIND_TRANSFER_READ'
...
external/drm_gralloc/gralloc_drm_pipe.c:104:11: error: use of undeclared identifier 'PIPE_BIND_TRANSFER_WRITE'
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes a building error introduced by commit 9daaa6f
"gallium: add a pipe_context parameter to resource_get_handle"
The new parameter was introduced for radeonsi future uses
and can be optionally set to NULL for now
|
|/
|
|
|
|
|
|
|
| |
Even if only swrast/llvmpipe is selected, there is still a dependency on
drm_gralloc. Removing the dependency seems to be too much work.
The path for the Mesa repo needs to be adapted.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
|
|
| |
The unsupported driver message was suppressed by a subtle bug
of commit cbf96c0d which treats the latest checking as an else
case. Remove the unnecessary else.
Besides, logically on entering ENABLE_PIPE snippet, drv is
always null. No need to check it.
|
|
|
|
|
|
|
|
|
|
|
| |
two drm handle may use same bo, but there is no
reference protect. if one of the drm handle release
the bo, another handle's bo become a wildpointer,
any read/write on the wildpointer will cause system
unstable, crash.
Change-Id: Ieaca522e3372dba82c48961499b9b657ca33cd15
Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
|
|
|
|
|
|
| |
and extend support beyong hdmi.
Change-Id: Ib9550eac0330807ccd4c3919609cbf02ad98299d
|
|
|
|
|
|
| |
Refactor code to support multiple mirrored outputs following code.
Change-Id: I60781d707ae68db2dbd2c4c4122b9183633a74be
|
|
|
|
|
|
|
| |
Rename it to drm_output_mode and move it into gralloc_drm_output
in preparation for folowing changes.
Change-Id: I488f395feede9c9a20eadb9145ebf46295ba4a71
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NO_REF_TASK
tested:
1) set persist.remixos.disp_best_fit to true
2) plugin the HDMI, the resolution should be the one fit the primary
screen (i.e. the resolution should be larger than or equal to primery
resolution, and it is the closest one)
3) set persist.remixos.disp_best_fit to false
4) plugin HDMI again, the external display will use the default
resolution.
Change-Id: I80b0fe6e7cc676ce1915f07f267204734bfc645f
|
|
|
|
| |
0x100 and 0x120 chipsets were added in gralloc_drm_nouveau.c
|
|
|
|
|
|
|
|
| |
Fixes a building error introduced by commit 82db518
"gallium: add external usage flags to resource_from(get)_handle (v2)"
parameter usage is required as a combination of PIPE_HANDLE_USAGE_* flags,
PIPE_HANDLE_USAGE_READ_WRITE was used as the most general case
|
|
|
|
| |
Change-Id: I398258147f9adcfbbcf2d92c7ba19887ea917bd0
|
|
|
|
|
|
| |
This reverts commit b19bbdbf98742f0428f6f4265b5e80d569608abd.
Change-Id: I351b1c3f149924f38635058004eb91d84351646a
|
|
|
|
| |
Change-Id: Ifc83db7bfe6f330ca68e4454516f7a84b2433823
|
|
|
|
| |
Change-Id: I4e83eb55f2813c92873b8481b8ae9328add4c4f7
|
|
|
|
|
|
|
|
| |
Current implementation prefers gralloc_drm_pipe over gralloc_drm_{driver}
while it may be the target solution, for nouveau it causes problems
because it is not anymore possible to use gralloc_drm_nouveau
whenever there is a driver ( e.g. swrast) in BoardConfig.mk BOARD_GPU_DRIVERS
not matching the list of valid drivers in drm_gralloc Android.mk
|
|
|
|
|
|
|
| |
Check load_pipe_screen for NULL and return in case dlsym returns a NULL
pointer. This can happen if the correct gallium driver is not enabled.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
|
|
|
|
|
| |
On x86 there was still a size mismatch due to x86-32 structs not following
natural alignment for 64-bit values. Force the alignment of the union.
Also, there appeared to be some padding on the end, so move the union to
the end of the struct.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
| |
Probably we don't need this quirk anymore?
|
|
|
|
| |
This partially reverts commit dc21193e3252ba2d6526546ba1d0c02116baf3ee.
|
|
|
|
|
|
| |
With the load_pipe_screen support, these libraries are no longer needed.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
|
|
|
| |
Build pipe support by default when any unlisted driver is enabled. This way
gralloc doesn't have to be updated for every new driver.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
|
|
| |
Note entirely sure what synchronization guarantees android provides
before calling in to module.. but stuff inside gralloc module is
definately not thread-safe so slap a big lock around the outside.
|
|
|
|
|
|
| |
Mesa EGL needs to retrieve prime fds from gralloc handles.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
|
|
|
| |
Based on Rob Clark's work to avoid duplicating gallium driver loading
code and statically linking each driver's pipe and winsys libraries.
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
| |
Signed-off-by: Rob Herring <robh@kernel.org>
|
|
|
|
|
|
|
| |
gralloc_drm_handle_t size differs for 32/64 bit process. thus on
x86_64, this will crash any 32bit app, add propper padding.
Change-Id: I03663b36dd841bf69c84973fd2f5e99741317c15
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As highlighted by pstglia current definition of GRALLOC_DRM_HANDLE_NUM_INTS
causes issues with 64-bit, because a pointer is accounted as having size of
an integer, which is not applicable to 64-bit pointer
The same definition adopted in AOSP hardware/drm_gralloc master branch has
been used, without changing the structure of gralloc_drm_handle_t.
|
| |
| |
| |
| | |
This reverts commit 3e00d3255ba6de08761a6b8f40b838680d502d0b.
|
|/
|
|
|
| |
Change-Id: If640f6ad7c6b904df59b5c5e164f184f1fc97170
Signed-off-by: Sean Paul <seanpaul@chromium.org>
|
|
|
|
| |
Rather than accessing gralloc_drm_pid directly.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It could be wrong to cast a pointer to a long type
(32-bit signed integer) and extend it to a uint64_t
(64-bit unsigned integer).
Cast it to uintptr_t as the xorg-video-ati does.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- HAWAII and MULLINS added
- changed 0x9649 from CHIP_FAMILY_SUMO to CHIP_FAMILY_SUMO2
- added missing chipInfo for CHIP_FAMILY_VERDE, CHIP_FAMILY_OLAND, CHIP_FAMILY_BONAIRE and CHIP_FAMILY_KAVERI
|
| |
| |
| |
| |
| |
| |
| | |
It allows the camera to get a lock on the buffer.
This is required when a picture is taken.
Credited to Edgardo Gho <edgardogho@gmail.com>.
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Seems it is buggy.
|
| |
| |
| |
| | |
Now the include paths are imported automatically from libdrm*.
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When allocating a new buffer using pipe driver, pipe constants
are used to define a format based on corresponding HAL_PIXEL_FORMAT
However, vmwgfx driver expects other constants
(SVGA3D_A8R8G8B8, SVGA3D_X8R8G8B8, SVGA3D_R5G6B5, etc)
Changed the returning constants to match what driver expects.
v2: [cwhuang]
- Use the constants defined in svga3d_types.h.
- Use C99 standard to avoid building errors with mesa 10.6.
|
| |
| |
| |
| | |
Based on the work by pstglia.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on some work by pstglia, one needs to switch off (partially or
fully?) the tiling when creating the BO.
Comment/uncomment the SW_INDICATOR_FULLY_DISABLES_TILING define to
toggle between the two.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
|