All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nico Schottelius <nico-linux-20120419@schottelius.org>,
	Francois Rigaut <frigaut@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor
Date: Thu, 3 May 2012 11:51:55 -0700	[thread overview]
Message-ID: <20120503185155.GA554@kroah.com> (raw)
In-Reply-To: <20120503184008.GB9432@schottelius.org>

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

  reply	other threads:[~2012-05-03 18:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 16:38 Linux Support for Thunderbolt using Apple Monitor Nico Schottelius
2012-04-19 21:15 ` Greg KH
     [not found] ` <CAMVeQ8r_3vuAxzbLyKoecOHOOGijUDkLfw+MK7o-WoWbuOGSrg@mail.gmail.com>
2012-05-02 16:36   ` Nico Schottelius
2012-05-02 20:25     ` Greg KH
2012-05-03  6:50       ` Nico Schottelius
2012-05-03 15:34         ` Greg KH
     [not found]         ` <CAMVeQ8qYu4bShd_+pwRv8bShhusJMDa-jjoqu7EujS4jt7RSNA@mail.gmail.com>
2012-05-03 15:35           ` Greg KH
2012-05-03 18:40             ` Nico Schottelius
2012-05-03 18:51               ` Greg KH [this message]
     [not found]             ` <CAMVeQ8q3PMMGmFSgrnqbW2HVdfmN+LgatX3TSfv5_2Ebuuj=QQ@mail.gmail.com>
2012-05-03 23:38               ` Greg KH
2012-05-04  4:19                 ` Francois Rigaut
2012-05-04 18:48                   ` Greg KH
2012-05-04 19:37                     ` Yinghai Lu
2012-05-04 19:38                       ` Yinghai Lu
2012-05-05  4:19                         ` Francois Rigaut
2012-05-05  8:18                           ` Jiang Liu
2012-05-05  8:47                             ` Francois Rigaut
2012-05-05 15:27                               ` Jiang Liu
2012-05-05 15:18                           ` Jiang Liu
2012-05-05 16:48                             ` Nico Schottelius
2012-05-06  3:22                               ` Jiang Liu
2012-05-09 16:05                                 ` Greg KH
2012-05-10  1:49                                   ` Francois Rigaut
2012-05-10  3:45                                     ` Greg KH
2012-05-06  3:59                             ` Francois Rigaut
2012-05-05  0:28                     ` Francois Rigaut
2012-05-05  0:35                       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120503185155.GA554@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=frigaut@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-linux-20120419@schottelius.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.