On 29 November 2015 at 12:47, Daniel Vetter wrote:
> On Fri, Nov 27, 2015 at 07:37:53PM -0500, Ilia Mirkin wrote:
>> On Fri, Nov 27, 2015 at 10:40 AM, Emil Velikov
>> wrote:
>> > On 27 November 2015 at 15:10, Daniel Vetter wrote:
>> >> It only leads to bloodshed and tears - we don't bother to r
On Fri, Nov 27, 2015 at 07:37:53PM -0500, Ilia Mirkin wrote:
> On Fri, Nov 27, 2015 at 10:40 AM, Emil Velikov
> wrote:
> > On 27 November 2015 at 15:10, Daniel Vetter wrote:
> >> It only leads to bloodshed and tears - we don't bother to restore a
> >> working legacy vga hw setup.
> >>
> >> On ha
On Fri, Nov 27, 2015 at 10:40 AM, Emil Velikov wrote:
> On 27 November 2015 at 15:10, Daniel Vetter wrote:
>> It only leads to bloodshed and tears - we don't bother to restore a
>> working legacy vga hw setup.
>>
>> On haswell with the new dynamic power well code this leads to even
>> more hilari
On 27 November 2015 at 15:10, Daniel Vetter wrote:
> It only leads to bloodshed and tears - we don't bother to restore a
> working legacy vga hw setup.
>
> On haswell with the new dynamic power well code this leads to even
> more hilarity since for some configurations the hardware is simply no
> l
It only leads to bloodshed and tears - we don't bother to restore a
working legacy vga hw setup.
On haswell with the new dynamic power well code this leads to even
more hilarity since for some configurations the hardware is simply no
longer there.
The actual implementation is a bit a hack - we re
