From: Simon Guinot <simon.guinot@sequanux.org>
To: "Levy, Amir (Jer)" <amir.jer.levy@intel.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"mario_limonciello@dell.com" <mario_limonciello@dell.com>,
thunderbolt-linux <thunderbolt-linux@intel.com>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
"Zhang, Xiong Y" <xiong.y.zhang@intel.com>,
"Jamet, Michael" <michael.jamet@intel.com>,
remi.rerolle@seagate.com
Subject: Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking
Date: Tue, 15 Nov 2016 11:59:21 +0100 [thread overview]
Message-ID: <20161115105920.GH6167@kw.sim.vm.gnt> (raw)
In-Reply-To: <E607265CB020454880711A6F96C05A03B677E4C9@hasmsx107.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 4442 bytes --]
On Wed, Nov 09, 2016 at 03:42:53PM +0000, Levy, Amir (Jer) wrote:
> On Wed, Nov 9 2016, 04:36 PM, Simon Guinot wrote:
> > On Wed, Nov 09, 2016 at 04:20:00PM +0200, Amir Levy wrote:
> > > This driver enables Thunderbolt Networking on non-Apple platforms
> > > running Linux.
> > >
> > > Thunderbolt Networking provides peer-to-peer connections to transfer
> > > files between computers, perform PC migrations, and/or set up small
> > > workgroups with shared storage.
> > >
> > > This is a virtual connection that emulates an Ethernet adapter that
> > > enables Ethernet networking with the benefit of Thunderbolt
> > > superfast medium capability.
> > >
> > > Thunderbolt Networking enables two hosts and several devices that
> > > have a Thunderbolt controller to be connected together in a linear
> > > (Daisy
> > > chain) series from a single port.
> > >
> > > Thunderbolt Networking for Linux is compatible with Thunderbolt
> > > Networking on systems running macOS or Windows and also supports
> > > Thunderbolt generation 2 and 3 controllers.
> > >
> > > Note that all pre-existing Thunderbolt generation 3 features, such
> > > as USB, Display and other Thunderbolt device connectivity will
> > > continue to function exactly as they did prior to enabling Thunderbolt Networking.
> > >
> > > Code and Software Specifications:
> > > This kernel code creates a virtual ethernet device for computer to
> > > computer communication over a Thunderbolt cable.
> > > The new driver is a separate driver to the existing Thunderbolt driver.
> > > It is designed to work on systems running Linux that interface with
> > > Intel Connection Manager (ICM) firmware based Thunderbolt
> > > controllers that support Thunderbolt Networking.
> > > The kernel code operates in coordination with the Thunderbolt user-
> > > space daemon to implement full Thunderbolt networking functionality.
> > >
> > > Hardware Specifications:
> > > Thunderbolt Hardware specs have not yet been published but are used
> > > where necessary for register definitions.
> >
> > Hi Amir,
> >
> > I have an ASUS "All Series/Z87-DELUXE/QUAD" motherboard with a
> > Thunderbolt 2 "Falcon Ridge" chipset (device ID 156d).
> >
> > Is the thunderbolt-icm driver supposed to work with this chipset ?
> >
>
> Yes, the thunderbolt-icm supports Falcon Ridge, device ID 156c.
> 156d is the bridge - http://lxr.free-electrons.com/source/include/linux/pci_ids.h#L2619
>
> > I have installed both a 4.8.6 Linux kernel (patched with your v9
> > series) and the thunderbolt-software-daemon (27 october release)
> > inside a Debian system (Jessie).
> >
> > If I connect the ASUS motherboard with a MacBook Pro (Thunderbolt 2,
> > device ID 156c), I can see that the thunderbolt-icm driver is loaded
> > and that the thunderbolt-software-daemon is well started. But the
> > Ethernet interface is not created.
> >
> > I have attached to this email the syslog file. There is the logs from
> > both the kernel and the daemon inside. Note that the daemon logs are
> > everything but clear about what could be the issue. Maybe I missed
> > some kind of configuration ? But I failed to find any valuable
> > information about configuring the driver and/or the daemon in the various documentation files.
> >
> > Please, can you provide some guidance ? I'd really like to test your
> > patch series.
>
> First, thank you very much for willing to test it.
> Thunderbolt Networking support was added during Falcon Ridge, in the latest FR images.
> Do you know which Thunderbolt image version you have on your system?
> Currently I submitted only Thunderbolt Networking feature in Linux, and we plan to add
> more features like reading the image version and updating the image.
> If you don't know the image version, the only thing I can suggest is to load windows, install thunderbolt SW
> and check in the Thunderbolt application the image version.
> To know if image update is needed, you can check - https://thunderbolttechnology.net/updates
Hi Amir,
From the Windows Thunderbolt software, I can read 13.00 for the firmware
version. And from https://thunderbolttechnology.net/updates, I can see
that there is no update available for my ASUS motherboard.
Am I good to go ?
BTW, it is quite a shame that the Thunderbolt firmware version can't be
read from Linux.
Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-11-15 10:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:20 [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 1/8] thunderbolt: Macro rename Amir Levy
2016-11-09 14:20 ` [PATCH v9 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-11-09 14:20 ` [PATCH v9 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-11-09 14:20 ` [PATCH v9 4/8] thunderbolt: Networking state machine Amir Levy
2016-11-09 14:20 ` [PATCH v9 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-11-09 14:20 ` [PATCH v9 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 7/8] thunderbolt: Networking doc Amir Levy
2016-11-09 16:00 ` Greg KH
2016-11-10 11:47 ` Levy, Amir (Jer)
2016-11-10 11:53 ` Greg KH
2016-11-10 14:24 ` Jonathan Corbet
2016-11-09 14:20 ` [PATCH v9 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-11-09 14:36 ` [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Simon Guinot
2016-11-09 15:42 ` Levy, Amir (Jer)
2016-11-15 10:59 ` Simon Guinot [this message]
2016-11-18 8:48 ` Levy, Amir (Jer)
2016-11-18 10:07 ` gregkh
2016-11-20 6:30 ` Levy, Amir (Jer)
2016-11-21 12:22 ` gregkh
2016-11-18 11:20 ` Simon Guinot
2016-11-22 17:28 ` Simon Guinot
2016-11-22 17:36 ` Mario.Limonciello
2016-11-24 20:35 ` Levy, Amir (Jer)
2016-11-09 16:02 ` Greg KH
2016-11-10 11:39 ` Levy, Amir (Jer)
2016-11-10 11:44 ` Greg KH
2016-11-10 11:48 ` Levy, Amir (Jer)
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=20161115105920.GH6167@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.org \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=remi.rerolle@seagate.com \
--cc=thunderbolt-linux@intel.com \
--cc=tomas.winkler@intel.com \
--cc=xiong.y.zhang@intel.com \
/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).