linux-kernel - Re: Linux Support for Thunderbolt using Apple Monitor

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] [day] [month] [year] [list]

Message-ID: <20120503185155.GA554@kroah.com>
Date:	Thu, 3 May 2012 11:51:55 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Nico Schottelius <nico-linux-20120419@...ottelius.org>,
	Francois Rigaut <frigaut@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor

On Thu, May 03, 2012 at 08:40:08PM +0200, Nico Schottelius wrote:
> Greg,
> 
> Greg KH [Thu, May 03, 2012 at 08:35:47AM -0700]:
> > [...]
> > 
> > How about if you load the acpiphp module instead?  Some BIOSes use that
> > instead of pciehp.
> > 
> > You need one of those drivers in order for this to work properly.
> > 
> > Also, speaking of BIOS, make sure you have the latest updates, there
> > were a lot of initial problems with Thunderbolt hotplug issues that were
> > fixed in newer BIOS versions, so that will be required to be updated.
> 
> I'm confused - to which BIOS are you referring to? I understood that
> Apple's Mac Book Air has its custom "similar to EFI" (*) code and not a
> traditional BIOS in place.

It's still a BIOS, and needs to be updated.  If that BIOS boots using
EFI or the "old" format is not an issue here.

> (*) Which would also be interesting to replace with something like
>     LinuxBios/Coreboot.

Good luck with that :)

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/