On 26 August 2016 at 04:04, Kevin Brace wrote:
> Hi Emil,
>
>> Hi Kevin,
>>
>> On 26 August 2016 at 01:19, Kevin Brace wrote:
>>
>> > I do not want to be seen as stopping progress, but there are still people
>> > who use less than current hardware (myself and countless others) or non
>> > Big 3
On 4 August 2016 at 18:06, David Herrmann wrote:
> The legacy DRI1 drivers expose highly broken interfaces to user-space. No
> modern system should enable them, or you will effectively allow user-space
> to circumvent most of your kernel security measures. The DRI1 kernel APIs
> are simply broken.
Hi Connor,
> > r128 is 90% the same as early radeons so it would make sense to add
> > support to radeon.
> >
> > Alex
>
> Ccing Kevin Brace.
>
> The drivers were removed from mesa and "you won't have to freeze your
> kernel or anything" was one of the justifications given at the time for
> why
Hi Emil,
> Hi Kevin,
>
> On 26 August 2016 at 01:19, Kevin Brace wrote:
>
> > I do not want to be seen as stopping progress, but there are still people
> > who use less than current hardware (myself and countless others) or non Big
> > 3 x86 graphics (NVIDIA, AMD, and Intel) for things like t
Hi Kevin,
On 26 August 2016 at 01:19, Kevin Brace wrote:
> I do not want to be seen as stopping progress, but there are still people who
> use less than current hardware (myself and countless others) or non Big 3 x86
> graphics (NVIDIA, AMD, and Intel) for things like thin clients.
[snip]
> A
Hi David,
> Lets move forward and hide the remaining DRI1 drivers behind a config
> option, so we have a central place to disable them all. Furthermore, we
> can provide a clear warning to anyone enabling them.
>
> Signed-off-by: David Herrmann
> ---
> drivers/gpu/drm/Kconfig | 135
> +
On 25 August 2016 at 12:14, Daniel Vetter wrote:
> On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
>> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
>> > The legacy DRI1 drivers expose highly broken interfaces to user-space. No
>> > modern system should enable them,
On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
> > The legacy DRI1 drivers expose highly broken interfaces to user-space. No
> > modern system should enable them, or you will effectively allow user-space
> > to circumv
On 25/08/16 11:13 AM, Alex Deucher wrote:
> On Thu, Aug 25, 2016 at 11:04 AM, Emil Velikov
> wrote:
>> On 25 August 2016 at 12:14, Daniel Vetter wrote:
>>> On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
> The
On Thu, Aug 25, 2016 at 11:04 AM, Emil Velikov
wrote:
> On 25 August 2016 at 12:14, Daniel Vetter wrote:
>> On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
>>> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
>>> > The legacy DRI1 drivers expose highly broken interfa
The legacy DRI1 drivers expose highly broken interfaces to user-space. No
modern system should enable them, or you will effectively allow user-space
to circumvent most of your kernel security measures. The DRI1 kernel APIs
are simply broken.
User-space can always use vesafb/efifb/simplefb and frie
On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
> The legacy DRI1 drivers expose highly broken interfaces to user-space. No
> modern system should enable them, or you will effectively allow user-space
> to circumvent most of your kernel security measures. The DRI1 kernel APIs
> are
12 matches
Mail list logo
