public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Francois Rigaut <frigaut@gmail.com>
Cc: Jiang Liu <liuj97@gmail.com>,
	Nico Schottelius <nico-linux-20120419@schottelius.org>,
	Yinghai Lu <yinghai@kernel.org>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor
Date: Wed, 9 May 2012 20:45:03 -0700	[thread overview]
Message-ID: <20120510034503.GB18543@kroah.com> (raw)
In-Reply-To: <4FAB1EAF.2090305@gmail.com>

On Thu, May 10, 2012 at 11:49:35AM +1000, Francois Rigaut wrote:
> Greg,
> 
> I went ahead and contacted John Ronciak at intel.
> He gave a presentation on thunderbolt at the 2011 linux plumber conference.
> Here is his answer:
> 
> "You are correct that most if not all issues related to Thunderbolt
> on Linux is due to BIOS problems. We have not seen anything other
> BIOS issues regarding Thunderbolt issues on Linux. When the BIOS is
> working correctly the hot-plug PCIe works fine wrt the kernel. These
> are things that cannot be fixed in the drivers or in kernel
> infrastructure. So newer systems are going to be better than older
> ones due to these BIOS issues."

Thanks for letting us know, so there's nothing we can do for these
machines, and we just have to hope the next-generation machines get this
correct.

greg k-h

  reply	other threads:[~2012-05-10  3:45 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
     [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 [this message]
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=20120510034503.GB18543@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=frigaut@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=nico-linux-20120419@schottelius.org \
    --cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox