From: Thomas Gleixner <tglx@linutronix.de>
To: "Hall, Christopher S" <christopher.s.hall@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Richard Cochran <richardcochran@gmail.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"john.stultz@linaro.org" <john.stultz@linaro.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: RE: [PATCH v3 1/4] Add correlated clocksource deriving system time from an auxiliary clocksource
Date: Sat, 5 Sep 2015 10:46:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509051044040.15006@nanos> (raw)
In-Reply-To: <B79D786B7111A34A8CF09F833429C493A90B2FDE@ORSMSX109.amr.corp.intel.com>
On Fri, 4 Sep 2015, Hall, Christopher S wrote:
> > Right, but we still do not know how that is going to be used. And
> > that's the key question. As long as that is not answered all can do is
> > wild guessing.
>
> It's not wild guessing. We do have it working on other OSs and have
> a pretty good idea of how it will work. The DSP firmware will be
> largely identical for Linux. I think now, we have a chicken and egg
> problem.
You have a totally different problem. You are just refusing to explain
how all that stuff is supposed to work and what kind of functionality
you need exactly.
Is it that hard to describe the technical requirements and the
presumably assbackwards restrictions of the firmware?
Thanks,
tglx
next prev parent reply other threads:[~2015-09-05 8:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:52 [PATCH v3 0/4] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2015-08-21 18:52 ` [PATCH v3 1/4] Add correlated clocksource deriving system time from an auxiliary clocksource Christopher S. Hall
2015-08-22 20:17 ` Thomas Gleixner
2015-09-03 23:20 ` Hall, Christopher S
2015-09-04 8:11 ` Richard Cochran
2015-09-04 14:28 ` Peter Zijlstra
2015-09-04 21:12 ` Hall, Christopher S
2015-09-04 13:02 ` Thomas Gleixner
2015-09-04 15:10 ` Peter Zijlstra
2015-09-04 15:17 ` Richard Cochran
2015-09-04 15:41 ` Peter Zijlstra
2015-09-04 16:35 ` Thomas Gleixner
2015-09-04 21:01 ` Hall, Christopher S
2015-09-05 8:46 ` Thomas Gleixner [this message]
2015-09-05 10:04 ` Ingo Molnar
2015-09-04 15:32 ` Richard Cochran
2015-09-04 21:50 ` John Stultz
2015-08-21 18:52 ` [PATCH v3 2/4] Added ART correlated clocksource and ART CPU feature Christopher S. Hall
2015-08-22 20:26 ` Thomas Gleixner
2015-08-21 18:52 ` [PATCH v3 3/4] Add support for driver cross-timestamp to PTP_SYS_OFFSET ioctl Christopher S. Hall
2015-08-22 20:33 ` Thomas Gleixner
2015-08-22 21:17 ` Richard Cochran
2015-08-23 8:15 ` Thomas Gleixner
2015-08-23 11:25 ` Richard Cochran
2015-08-24 20:16 ` Hall, Christopher S
2015-08-25 7:31 ` Richard Cochran
2015-08-21 18:52 ` [PATCH v3 4/4] Enabling hardware supported PTP system/device crosstimestamping Christopher S. Hall
2015-08-22 20:46 ` Thomas Gleixner
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=alpine.DEB.2.11.1509051044040.15006@nanos \
--to=tglx@linutronix.de \
--cc=christopher.s.hall@intel.com \
--cc=hpa@zytor.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=richardcochran@gmail.com \
--cc=x86@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