On Wed, Jul 20, 2016 at 10:34 PM, Rob Herring wrote:
> On Wed, Jul 20, 2016 at 12:53 AM, Tomasz Figa wrote:
>> On Wed, Jul 20, 2016 at 7:40 AM, Rob Herring wrote:
>>> On Fri, Jul 15, 2016 at 2:53 AM, Tomasz Figa wrote:
If no hardware driver is present, it is possible to fall back to
t
On Wed, Jul 20, 2016 at 12:53 AM, Tomasz Figa wrote:
> On Wed, Jul 20, 2016 at 7:40 AM, Rob Herring wrote:
>> On Fri, Jul 15, 2016 at 2:53 AM, Tomasz Figa wrote:
>>> If no hardware driver is present, it is possible to fall back to
>>> the kms_swrast driver with any DRI node that supports dumb GE
On Wed, Jul 20, 2016 at 7:40 AM, Rob Herring wrote:
> On Fri, Jul 15, 2016 at 2:53 AM, Tomasz Figa wrote:
>> If no hardware driver is present, it is possible to fall back to
>> the kms_swrast driver with any DRI node that supports dumb GEM create
>> and mmap IOCTLs with softpipe/llvmpipe drivers.
On Fri, Jul 15, 2016 at 2:53 AM, Tomasz Figa wrote:
> If no hardware driver is present, it is possible to fall back to
> the kms_swrast driver with any DRI node that supports dumb GEM create
> and mmap IOCTLs with softpipe/llvmpipe drivers. This patch makes the
> Android EGL platform code retry pr
Tomasz Figa writes:
> If no hardware driver is present, it is possible to fall back to
> the kms_swrast driver with any DRI node that supports dumb GEM create
> and mmap IOCTLs with softpipe/llvmpipe drivers. This patch makes the
> Android EGL platform code retry probe with kms_swrast if hardware
If no hardware driver is present, it is possible to fall back to
the kms_swrast driver with any DRI node that supports dumb GEM create
and mmap IOCTLs with softpipe/llvmpipe drivers. This patch makes the
Android EGL platform code retry probe with kms_swrast if hardware-only
probe fails.
Signed-off
