From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH v2 0/8] Thunderbolt workarounds Date: Wed, 3 Jul 2013 22:21:08 +0100 Message-ID: <20130703212108.GA884@srcf.ucam.org> References: <1372860295-8306-1-git-send-email-mika.westerberg@linux.intel.com> <20130703182900.GA29079@srcf.ucam.org> <20130703183311.GA17340@kroah.com> <20130703184434.GA29587@srcf.ucam.org> <20130703203542.GA32736@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "Ronciak, John" Cc: Greg Kroah-Hartman , Mika Westerberg , Bjorn Helgaas , "Wysocki, Rafael J" , Jesse Barnes , Yinghai Lu , "Penner, Miles J" , "Allan, Bruce W" , Heikki Krogerus , "Kirill A. Shutemov" , "linux-kernel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "linux-pci@vger.kernel.org" , "x86@kernel.org" List-Id: linux-acpi@vger.kernel.org On Wed, Jul 03, 2013 at 08:46:57PM +0000, Ronciak, John wrote: > Apple does their own thing and do not talk to Intel about it at all. This includes writing special drivers and user-space components. So we (Intel) don't know so we can't comment about it. Sorry. The hardware has an Intel part number, so I'm pretty sure someone there has some idea what the register map looks like. -- Matthew Garrett | mjg59@srcf.ucam.org