All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "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>,
	"Nashif, Anas" <anas.nashif@intel.com>
Subject: Re: [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade)
Date: Tue, 01 Jul 2008 19:13:03 +0000	[thread overview]
Message-ID: <200807011213.03405.jesse.barnes@intel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0807011506450.18141@p34.internal.lan>

On Tuesday, July 01, 2008 12:08 pm Justin Piszcz wrote:
> >> 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.

Oh, great.  Good to hear we actually fix those bugs! :)

Thanks,
Jesse

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Jesse Barnes <jesse.barnes@intel.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "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>,
	"Nashif, Anas" <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 12:13:03 -0700	[thread overview]
Message-ID: <200807011213.03405.jesse.barnes@intel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0807011506450.18141@p34.internal.lan>

On Tuesday, July 01, 2008 12:08 pm Justin Piszcz wrote:
> >> 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.

Oh, great.  Good to hear we actually fix those bugs! :)

Thanks,
Jesse

  reply	other threads:[~2008-07-01 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 14:09 [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade) Justin Piszcz
2008-06-30 14:09 ` Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel? Justin Piszcz
2008-07-01 18:43 ` [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade) Justin Piszcz
2008-07-01 18:43   ` Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel? Justin Piszcz
2008-07-01 18:58   ` [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade) Jesse Barnes
2008-07-01 18:58     ` Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel? Jesse Barnes
2008-07-01 19:08     ` [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade) Justin Piszcz
2008-07-01 19:08       ` Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel? Justin Piszcz
2008-07-01 19:13       ` Jesse Barnes [this message]
2008-07-01 19:13         ` Jesse Barnes
2008-07-09 14:30         ` [lm-sensors] Intel DG965WH / Case 745-44-22 (slow bios/upgrade) Lennart Sorensen
2008-07-09 14:30           ` Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel? 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=200807011213.03405.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=anas.nashif@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jpiszcz@lucidpixels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.