[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1509051044040.15006@nanos>
Date: Sat, 5 Sep 2015 10:46:51 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Hall, Christopher S" <christopher.s.hall@...el.com>
cc: Peter Zijlstra <peterz@...radead.org>,
Richard Cochran <richardcochran@...il.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"john.stultz@...aro.org" <john.stultz@...aro.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: RE: [PATCH v3 1/4] Add correlated clocksource deriving system time
from an auxiliary clocksource
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists