Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757378Ab0HQJGT (ORCPT ); Tue, 17 Aug 2010 05:06:19 -0400 Received: from mail-bw0-f46.google.com ([209.85.214.46]:62429 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753567Ab0HQJGR (ORCPT ); Tue, 17 Aug 2010 05:06:17 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Tt+I7gHvEUgrkCRNm0q++wqI4JjG2LOIhMEtbHeamxTLSLLve3q4Ix6QxUgbOT4r3N taNVzGBjkrDmY4imJ6KmRUMJYvf5nb+bXg0DbDkR6frWOyXWThR8foFjYbdWqdUsVlJ9 oLMMPuaI38dqzYHBubN+QkieHGv1KaFTFT60c= Date: Tue, 17 Aug 2010 11:06:37 +0200 From: Richard Cochran To: Masayuki Ohtake Cc: meego-dev@meego.com, LKML Subject: Re: [MeeGo-dev] [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to 2.6.35 Message-ID: <20100817090637.GC3330@riccoc20.at.omicron.at> References: <4C612AA4.5040100@dsn.okisemi.com> <20100810171343.GE21220@suse.de> <002601cb3926$edaf24d0$66f8800a@maildom.okisemi.com> <20100811151510.GB9180@suse.de> <20100812020027.GA14121@suse.de> <001001cb3ddb$9929d9a0$66f8800a@maildom.okisemi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001001cb3ddb$9929d9a0$66f8800a@maildom.okisemi.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 558 Lines: 17 On Tue, Aug 17, 2010 at 04:12:45PM +0900, Masayuki Ohtake wrote: > Intel Topcliff IEEE1588 device driver API is developed according to Intel > Tolapai 1588 device driver. > Both APIs are the same. But what is the "Intel Tolapai 1588 device driver?" Is that a Linux driver? If so, where can I find it? Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/