Date: Thu, 21 Jun 2007 10:28:38 -0400 (EDT)
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
cc: Jesse Barnes <jbarnes@virtuousgeek.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trim memory not covered by WB MTRRs
In-Reply-To: <467A8A20.7000302@macroscoop.nl>
Message-ID: <Pine.LNX.4.64.0706211028320.31303@p34.internal.lan>
References: <200706071530.51552.jesse.barnes@intel.com>
 <200706141418.42082.jbarnes@virtuousgeek.org> <4672681D.7020601@macroscoop.nl>
 <200706150920.24490.jbarnes@virtuousgeek.org> <467A8A20.7000302@macroscoop.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1101
Lines: 34


On Thu, 21 Jun 2007, Pim Zandbergen wrote:

> Jesse Barnes wrote:
>>> 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...
>>
>> 
> I reported this to GigaByte, and lo and behold, they sent me a fixed BIOS 
> within 48 hours.
> Kudos to Taipeh!
>
> They sent the BIOS image in a private message, so it might take a while 
> before it's available
> on their website.
>
>

Wow, totally the opposite from Intel.

Justin.
-
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/