On 15.09.2016 13:37, Pekka Paalanen wrote:
> On Wed, 14 Sep 2016 11:50:34 +0200
> Armin Krezović wrote:
>
>> On 13.09.2016 12:49, Pekka Paalanen wrote:
>>> On Thu, 18 Aug 2016 18:42:32 +0200
>>> Armin Krezović wrote:
>>>
This is a complete port of the DRM backend that uses
recently
On Wed, 14 Sep 2016 11:50:34 +0200
Armin Krezović wrote:
> On 13.09.2016 12:49, Pekka Paalanen wrote:
> > On Thu, 18 Aug 2016 18:42:32 +0200
> > Armin Krezović wrote:
> >
> >> This is a complete port of the DRM backend that uses
> >> recently added output handling API for output
> >> configur
On 13.09.2016 12:49, Pekka Paalanen wrote:
> On Thu, 18 Aug 2016 18:42:32 +0200
> Armin Krezović wrote:
>
>> This is a complete port of the DRM backend that uses
>> recently added output handling API for output
>> configuration.
>>
>> Output can be configured at runtime by passing the
>> necessar
Hi
Found a few typos mentioned below.
On Thu, Aug 18, 2016 at 6:42 PM, Armin Krezović
wrote:
> This is a complete port of the DRM backend that uses
> recently added output handling API for output
*the* recently added [...]
> configuration.
>
> Output can be configured at runtime by passing the
On Thu, 18 Aug 2016 18:42:32 +0200
Armin Krezović wrote:
> This is a complete port of the DRM backend that uses
> recently added output handling API for output
> configuration.
>
> Output can be configured at runtime by passing the
> necessary configuration parameters, which can be
> filled in m
This is a complete port of the DRM backend that uses
recently added output handling API for output
configuration.
Output can be configured at runtime by passing the
necessary configuration parameters, which can be
filled in manually or obtained from the configuration
file using previously added fu
