From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs
Date: Fri, 15 Jun 2007 09:20:24 -0700
User-Agent: KMail/1.9.6
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
References: <200706071530.51552.jesse.barnes@intel.com> <200706141418.42082.jbarnes@virtuousgeek.org> <4672681D.7020601@macroscoop.nl>
In-Reply-To: <4672681D.7020601@macroscoop.nl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706150920.24490.jbarnes@virtuousgeek.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 960
Lines: 24

On Friday, June 15, 2007 3:21:17 Pim Zandbergen wrote:
> Jesse Barnes wrote:
> > Thanks for testing, Pim.  Glad it works for you.
>
> The pleasure was all on my side.
>
> > Keep an eye out for BIOS upgrades, the next version might fix it.
>
> What, are you going to report this to GigaByte?

No, but you should if you haven't already.  I think GigaByte probably 
gets its BIOS from another BIOS vendor (maybe Intel), so when that 
vendor provides them with an update, they'll probably provide it on 
their website.  And from what I understand, an Intel BIOS update is in 
the works to address this issue for Intel boards, so a GigaByte version 
may follow shortly.  I don't have an exact timeframe though...

Jesse

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/