mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Intel chooses not to support its HECI/QPS Chip in Linux?
Date: Sun, 4 Feb 2007 10:57:50 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702041050170.14035@p34.internal.lan> (raw)

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 bought an Intel board, thinking everything would be supported, because 
it is an Intel board.  The board is an Intel DG965WHMKR.  Is Intel 
changing its values around open source?  Digging around, one will read 
something regarding Intel loads a special piece of code in the firmware of 
the chip.  Seems anti-open-source to me.  I believe a lot of people are 
interested in viewing their temperature of their chipsets, cpu, etc within
Linux, currently this is not possible.

What if any other types of motherboards are really fully supported in 
Linux these days?  Suffice to say, I am a bit surprised Intel has been 
quietly ignoring this for quite some time now.

Some of the discussion that has been going on regarding this issue:

http://softwareforums.intel.com/ISN/Community/en-US/forums/thread/30225715.aspx

"Hello, Intel(r) Quiet System Technology (QST) support is provided by the 
Firmware running the Management Engine.  Linux support, however, is not 
currently planned for QST and so there is no HECI driver for Linux.  G. Holmes"

http://www.lm-sensors.org/ticket/2134
http://www.lm-sensors.org/ticket/2153

Can anyone provide any update?

Justin.


             reply	other threads:[~2007-02-04 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04 15:57 Justin Piszcz [this message]
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

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.0702041050170.14035@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®