mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, r.marek@assembler.cz
Subject: Intel chooses not to support its HECI/QPS Chip in Linux?
Date: Tue, 6 Mar 2007 07:53:56 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703060752390.29188@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0702050553080.29175@p34.internal.lan>



On Mon, 5 Feb 2007, Justin Piszcz wrote:

>
>
> On Mon, 5 Feb 2007, Arjan van de Ven wrote:
>
>> On Sun, 2007-02-04 at 10:57 -0500, Justin Piszcz wrote:
>>> Hi,
>>> 
>>> Anyone from Intel that reads LKML, could you provide an update as to what
>>> is happening with support for your HECI Controller/QPS chip, which is used
>>> on 965 (and possibly other?) chipsets.
>> 
>> I asked the right folks and the word I got was "Soon". The code we have
>> needs some major cleanups before it's suitable for lkml posting... but
>> it'll be there soon. We're working on the cleanups full time.... We'll
>> send an update when we're further along
>> 
>
> Very good news, thanks for the update!
>
> Justin.
>

It has been > 1 month since this last e-mail, I was wondering if anyone in 
the community [or Intel] could provide an update?  I spoke with one of the 
lmsensors the other day and he stated that there may be a plan to 
incorporate the CPU temperature soon, depending on what Intel does/what 
they provide.

Are we any closer to getting full HECI support in the kernel today than 
last month?

Justin.

      reply	other threads:[~2007-03-06 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04 15:57 Justin Piszcz
2007-02-04 18:46 ` Joseph Pingenot
2007-02-05  6:02 ` Arjan van de Ven
2007-02-05 10:54   ` Justin Piszcz
2007-03-06 12:53     ` Justin Piszcz [this message]

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=Pine.LNX.4.64.0703060752390.29188@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.marek@assembler.cz \
    /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

all inboxes | Powered by JetHome®