From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: <meego-dev@meego.com>, "LKML" <linux-kernel@vger.kernel.org>
Cc: "Wang, Yong Y" <yong.y.wang@intel.com>,
"Khor, Andrew Chih Howe" <andrew.chih.howe.khor@intel.com>,
<arjan@linux.intel.com>, "Greg KH" <gregkh@suse.de>,
"Wang, Qi" <qi.wang@intel.com>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to 2.6.35
Date: Tue, 17 Aug 2010 16:12:45 +0900 [thread overview]
Message-ID: <001001cb3ddb$9929d9a0$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A28EA272F@shsmsx501.ccr.corp.intel.com>
Sorry, for late response.
Please see out inline comments.
Thanks, Ohtake
----- Original Message -----
From: "Wang, Qi" <qi.wang@intel.com>
To: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
Cc: <meego-dev@meego.com>; "LKML" <linux-kernel@vger.kernel.org>; "Wang, Yong Y" <yong.y.wang@intel.com>; "Khor, Andrew
Chih Howe" <andrew.chih.howe.khor@intel.com>; <arjan@linux.intel.com>; "Greg KH" <gregkh@suse.de>
Sent: Thursday, August 12, 2010 11:15 AM
Subject: RE: [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to 2.6.35
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@suse.de]
> > Sent: Thursday, August 12, 2010 10:00 AM
> > To: Wang, Qi
> > Cc: Masayuki Ohtake; meego-dev@meego.com; LKML; Wang, Yong Y; Khor,
> > Andrew Chih Howe; arjan@linux.intel.com
> > Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to
> > 2.6.35
> >
> > On Thu, Aug 12, 2010 at 09:13:24AM +0800, Wang, Qi wrote:
> > > > -----Original Message-----
> > > > From: Greg KH [mailto:gregkh@suse.de]
> > > > Sent: Wednesday, August 11, 2010 11:15 PM
> > > > To: Masayuki Ohtake
> > > > Cc: meego-dev@meego.com; LKML; Wang, Qi; Wang, Yong Y; Khor, Andrew
> > > > Chih Howe; arjan@linux.intel.com
> > > > Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to
> > > > 2.6.35
> > > >
> > > > On Wed, Aug 11, 2010 at 04:29:25PM +0900, Masayuki Ohtake wrote:
> > > > > Hi Greg,
> > > > >
> > > > > > Do they all have to be ioctls? What exactly are they doing?
> > > > > I think using ioctl is common for this patch.
> > > >
> > > > "Common" is not ok, right?
> > > >
> > > > > Do you think that using ioctl is NOT appropriate for this patch?
> > > >
> > > > Yes.
> > > >
> > > > > Let me know your intension in more detail.
> > > >
> > > > Please express yours. Why do you feel you need these to be ioctls?
> > > > What exactly are they doing? Where is the documentation for them all?
> >
> > You forgot to answer this.
> Ohtake-san,
>
> Please answer this question asap.
Intel Topcliff IEEE1588 device driver API is developed according to Intel
Tolapai 1588 device driver.
Both APIs are the same.
> >
> > > > > > And are they 32/64bit safe?
> > > > > Only 32bit support.
> > > >
> > > > That's an obvious problem that needs to be resolved, right?
> > > The Tunnelcreak processor (A kind of Atom-based processor) only
> > > supports 32b, so PCH drivers only support 32b.
> > > They can make it 32/64 compatible, but it's difficult to test them,
> > > because there're no 64b Atom-based platform have those PCH devices.
> >
> > But that does not mean you should not be using the proper types and
> > other things necessary for proper ioctl usage.
> >
> > As you failed to describe what any of these ioctls do, I can't recommend
> > that you have any of them in the driver.
> Ohtake-san, Please solve 32b/64b safe issue asap.
> >
> > sorry,
> >
> > greg k-h
>
next prev parent reply other threads:[~2010-08-17 7:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 10:32 Masayuki Ohtak
2010-08-10 17:13 ` Greg KH
2010-08-10 17:37 ` Randy Dunlap
2010-08-11 1:20 ` Wang, Qi
2010-08-11 2:14 ` Masayuki Ohtake
2010-08-11 2:18 ` Wang, Qi
2010-08-11 2:31 ` Masayuki Ohtake
2010-08-11 5:49 ` Felipe Balbi
2010-08-11 6:31 ` Masayuki Ohtake
2010-08-11 7:29 ` Masayuki Ohtake
2010-08-11 15:15 ` Greg KH
2010-08-12 1:13 ` Wang, Qi
2010-08-12 2:00 ` Greg KH
2010-08-12 2:15 ` Wang, Qi
2010-08-17 7:12 ` Masayuki Ohtake [this message]
2010-08-17 9:06 ` [MeeGo-dev] " Richard Cochran
2010-08-17 11:25 ` Arnd Bergmann
2010-12-14 7:46 ` [MeeGo-dev][PATCH] " Tomoya MORINAGA
2010-12-14 16:21 ` Richard Cochran
2010-12-15 10:52 ` Tomoya MORINAGA
2010-08-17 13:07 ` [MeeGo-Dev][PATCH] " Greg KH
2010-08-13 8:07 ` [MeeGo-dev] " Richard Cochran
2010-08-11 9:08 ` Robert Schwebel
2010-08-11 10:45 ` [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to2.6.35 Masayuki Ohtake
2010-08-12 9:43 ` Richard Cochran
2010-08-11 4:34 [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to 2.6.35 Masayuki Ohtake
2010-08-11 4:39 ` Greg KH
2010-08-11 6:30 ` Masayuki Ohtake
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='001001cb3ddb$9929d9a0$66f8800a@maildom.okisemi.com' \
--to=masa-korg@dsn.okisemi.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=arjan@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=meego-dev@meego.com \
--cc=qi.wang@intel.com \
--cc=yong.y.wang@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
Powered by JetHome