On 22 February 2016 at 15:48, Rob Herring wrote:
> On Thu, Feb 18, 2016 at 1:15 PM, Emil Velikov
> wrote:
>> On 18 February 2016 at 17:47, Rob Clark wrote:
>>> On Thu, Feb 18, 2016 at 11:48 AM, Emil Velikov
>>> wrote:
Hi Rob,
On 10 February 2016 at 22:56, Rob Herring wrote:
>>
On Thu, Feb 18, 2016 at 1:15 PM, Emil Velikov wrote:
> On 18 February 2016 at 17:47, Rob Clark wrote:
>> On Thu, Feb 18, 2016 at 11:48 AM, Emil Velikov
>> wrote:
>>> Hi Rob,
>>>
>>> On 10 February 2016 at 22:56, Rob Herring wrote:
Introduce load_pipe_screen() public entry point for other
On 18 February 2016 at 17:47, Rob Clark wrote:
> On Thu, Feb 18, 2016 at 11:48 AM, Emil Velikov
> wrote:
>> Hi Rob,
>>
>> On 10 February 2016 at 22:56, Rob Herring wrote:
>>> Introduce load_pipe_screen() public entry point for other code which
>>> dlopen()'s gralloc_dri.so for purposes of loadi
On Thu, Feb 18, 2016 at 11:48 AM, Emil Velikov wrote:
> Hi Rob,
>
> On 10 February 2016 at 22:56, Rob Herring wrote:
>> Introduce load_pipe_screen() public entry point for other code which
>> dlopen()'s gralloc_dri.so for purposes of loading a pipe_screen. This way
>> drm_gralloc can avoid static
Hi Rob,
On 10 February 2016 at 22:56, Rob Herring wrote:
> Introduce load_pipe_screen() public entry point for other code which
> dlopen()'s gralloc_dri.so for purposes of loading a pipe_screen. This way
> drm_gralloc can avoid static linking of each gallium winsys and driver,
> and avoid duplica
Introduce load_pipe_screen() public entry point for other code which
dlopen()'s gralloc_dri.so for purposes of loading a pipe_screen. This way
drm_gralloc can avoid static linking of each gallium winsys and driver,
and avoid duplicated logic to figure out which pipe driver to load.
This is based o
