From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: "crmotherboard@mailbox.intel.com"
<crmotherboard@mailbox.cps.intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
Anas Nashif <anas.nashif@intel.com>
Subject: Re: Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel?
Date: Tue, 1 Jul 2008 15:08:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807011506450.18141@p34.internal.lan> (raw)
In-Reply-To: <200807011158.46258.jesse.barnes@intel.com>
On Tue, 1 Jul 2008, Jesse Barnes wrote:
> On Tuesday, July 01, 2008 11:43 am Justin Piszcz wrote:
>>> This is from 2007:
>>> http://softwareblogs.intel.com/2007/04/13/intel-me-interface-heci-now-ava
>>> ilable/
>>>
>>> Their updated project page:
>>> http://www.openamt.org/
>>>
>>> Justin.
>>
>> The issue regarding accessing the hard drive menu was fixed by simpling
>> power cycling/rebooting the host.
>
> And the problem hasn't come back?
Correct, after several reboots, the problem has not come back, I can
access the HDD part of the BIOS w/out any issues.
>
>> All issues are now resolved (regarding the slow speed/memory/etc)..
>
> Hopefully there's a more recent BIOS available that doesn't need to trim the
> memory for you?
Erm, that is what I am trying to get across, version 1738 of the BIOS has
successfully solved the memory mapping/non-cachable memory issue.
>
>> Only other question left is the HECI support in the kernel.
>
> I'll defer that question to Anas, he's been handling the HECI stuff.
Thanks, a lot of people are probably curious where this is heading as
well, as it impacts purchasing decisions of people and whether one should
buy an Intel board if one cannot monitor the sensors on it (voltages/fan
speeds, etc)..
>
> Jesse
>
next prev parent reply other threads:[~2008-07-01 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 14:09 Justin Piszcz
2008-07-01 18:43 ` Justin Piszcz
2008-07-01 18:58 ` Jesse Barnes
2008-07-01 19:08 ` Justin Piszcz [this message]
2008-07-01 19:13 ` Jesse Barnes
2008-07-09 14:30 ` Lennart Sorensen
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.1.10.0807011506450.18141@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=anas.nashif@intel.com \
--cc=crmotherboard@mailbox.cps.intel.com \
--cc=dan.j.williams@intel.com \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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
Powered by JetHome