public inbox for linux-kernel@vger.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 08:34:11 -0700	[thread overview]
Message-ID: <20120503153411.GC20334@kroah.com> (raw)
In-Reply-To: <20120503065003.GB13386@schottelius.org>

On Thu, May 03, 2012 at 08:50:03AM +0200, Nico Schottelius wrote:
> Greg KH [Wed, May 02, 2012 at 01:25:09PM -0700]:
> > Thunderbolt should show up to the kernel just as a "normal" PCIE link,
> > so there shouldn't be anything special we need to do to handle this at
> > all (or at least my Intel contacts said that.)
> 
> Well, at least from my lspci point of view (before/after disconnect same
> output), this seems to be wrong (no dmesg output as well).
> 
> Additionally as far as I understand
> thunderbolt, it's bundling display port and pci-e into a single channel,
> so I'm not sure if this is 100% transparent pci-e + displayport from our
> side.
> 
> Or, the better question is probably: How should Linux realise that there
> is a change (apple monitor with ethernet, usb, co. plugged in) going on?
> 
> > Note, I haven't tested this yet, so I can't verify it, but if you have
> > the hardware, you should be able to.
> 
> I can test stuff here, but would be thankful for a round of pointers on
> how to debug / approach this.

Have you loaded the pciehp module (or maybe acpiphp, depending on your
BIOS)?  One of those should be what will control the pci hotplug for
your system to work properly.

thanks,

greg k-h

  reply	other threads:[~2012-05-03 15:34 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 [this message]
     [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
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=20120503153411.GC20334@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox