lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2efea088-fb11-0daf-8c39-f7691e2cf075@fnarfbargle.com>
Date:   Wed, 28 Aug 2019 17:34:00 +0800
From:   Brad Campbell <lists2009@...rfbargle.com>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     linux-kernel@...r.kernel.org, michael.jamet@...el.com,
        YehezkelShB@...il.com
Subject: Re: Thunderbolt DP oddity on v5.2.9 on iMac 12,2

On 28/8/19 5:12 pm, Brad Campbell wrote:
> On 28/8/19 3:33 pm, Mika Westerberg wrote:

>> I'm suspecting that the boot firmware does configure second DP path also
>> and we either fail to discover it properly or the boot firmware fails to
>> set it up.
>>
>> Also if you boot with one monitor connected and then connect another
>> (when the system is up) does it work then?
> 
> Umm.. so this is where it gets weird. No it doesn't. Apparently it fails 
> to configure the first monitor it finds. This is the one the Apple 
> bootcamp firmware configures at boot.
> 

Ok just to clarify it appears I've been booting EFI and bypassing the 
Bootcamp BIOS emulation for a few years. So, that made no difference.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ