From: Nico Schottelius <nico-linux-20120419@schottelius.org>
To: Francois Rigaut <frigaut@gmail.com>
Cc: Nico Schottelius <nico-linux-20120419@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor
Date: Wed, 2 May 2012 18:36:29 +0200 [thread overview]
Message-ID: <20120502163629.GE928@schottelius.org> (raw)
In-Reply-To: <CAMVeQ8r_3vuAxzbLyKoecOHOOGijUDkLfw+MK7o-WoWbuOGSrg@mail.gmail.com>
Hey Francois,
Francois Rigaut [Mon, Apr 30, 2012 at 11:45:52AM +1000]:
> I have a MBA 13" (mid 2011), and I believe we already have been in contact
> about the state of linux on it. Thanks for your early work on it, it helped
> me quite a bit in the initial setup.
Great to have helped!
> I agree with you that linux is now pretty stable on MBAs. I'm exclusively
> running linux on mine, and beside the thunderbold/displayport support issue
> (that's why I am replying to this thread), I have been more than happy with
> it. btw, I don't experience the X crashes myself, and the network (both
> wired and wireless) is working flawlessly.
Network is mostly working fine nowadays as well, besides having to issue
"reassociate" in wpa_cli after each resume/suspend and a new bug in Xorg
that forces me to "rmmod bcm5974; modprobe bcm5974;" to make Xorg
recognsie the touchpad again (speaking of Linux 3.3.3-1-ARCH and
X.Org X Server 1.12.1 and xf86-input-synaptics 1.5.99.904-1).
> Now to the thunderbolt support: I have myself a thunderbolt 27" at work. In
> a nutshell: [...]
This smells exactly like in the old Linux days, when an external monitor
only worked when it was connected at startup.
I've tried to get some information about thunderbolt, but it seems Intel
is currently unwillingly to give information out:
http://communities.intel.com/message/155263#155263
I'm wondering if anyone from the Intel developers reading this list
can comment on this?
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next prev parent reply other threads:[~2012-05-02 19:04 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 [this message]
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
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=20120502163629.GE928@schottelius.org \
--to=nico-linux-20120419@schottelius.org \
--cc=frigaut@gmail.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).