[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BLU177-W18D4117284A1222D08D213C3E70@phx.gbl>
Date: Fri, 1 Aug 2014 02:54:34 -0700
From: Yuhong Bao <yuhongbao_386@...mail.com>
To: "H. Peter Anvin" <hpa@...or.com>,
"jerry.hoemann@...com" <jerry.hoemann@...com>
CC: "rob@...dley.net" <rob@...dley.net>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"x86@...nel.org" <x86@...nel.org>,
"matt.fleming@...el.com" <matt.fleming@...el.com>,
"yinghai@...nel.org" <yinghai@...nel.org>,
"penberg@...nel.org" <penberg@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"vgoyal@...hat.com" <vgoyal@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mjg59@...f.ucam.org" <mjg59@...f.ucam.org>
Subject: RE: [PATCH 0/3] Early use of boot service memory
>> I think i can go to a date based black list, that removes the manual
>> step. System running firmware before certain date assumes we need
>> to do the work around. If firmware is newer than that date, we don't
>> use the workaround. Blacklist overrides and allows current behavior
>> for new firmware that is subsequently found to be broken and for
>> which we can't convenience the manufacturer to fix.
>>
>
> No, we can't, at least not for now. We are continually finding new
> platforms with the bug.
What about now?
ot, but this is a fun read:
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkcentre_bios/9sjy81usa.txt
Notice the reference to "redhat 6.3"! --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists