From: Doug Thompson <norsk5@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Gross, Mark" <mark.gross@intel.com>
Cc: bluesmoke-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
"Carbonari, Steven" <steven.carbonari@intel.com>,
"Ong, Soo Keong" <soo.keong.ong@intel.com>,
"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>
Subject: Re: Problems with EDAC coexisting with BIOS
Date: Mon, 24 Apr 2006 10:38:18 -0700 (PDT) [thread overview]
Message-ID: <20060424173818.10362.qmail@web50103.mail.yahoo.com> (raw)
In-Reply-To: <1145884747.29648.35.camel@localhost.localdomain>
--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> At the very least we should print a warning advising the user that the
> BIOS is incompatible and to ask the BIOS vendor for an update so that
> they can enable error detection and management support.
Asking for the update might prompt for an update to actually be generated, but I
doubt it.
>
> Is only the AMI BIOS this braindamaged, should we just blacklist AMI
> bioses in EDAC or is this shared Intel supplied code that may be found
> in other vendors systems.
The engineer who wrote the E752X driver (originally from bluesmoke) was a LinuxBIOS
engineer. We do make some systems with factory BIOS, but not as many as with
LinuxBIOS. We might see these issues on those factory BIOS system, but none that I
know of.
doug thompson
>
> Alan
>
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you
want and they will surprise you with their ingenuity."
Gen George Patton
next prev parent reply other threads:[~2006-04-24 17:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 16:01 Gross, Mark
2006-04-21 21:13 ` Ingo Oeser
2006-04-24 13:19 ` Alan Cox
2006-04-24 17:38 ` Doug Thompson [this message]
2006-04-21 20:57 Doug Thompson
2006-04-21 21:32 Gross, Mark
2006-04-21 21:42 Doug Thompson
2006-04-21 22:20 Gross, Mark
2006-04-22 18:31 ` Tim Small
2006-04-21 22:36 Doug Thompson
2006-04-23 1:44 Gross, Mark
2006-04-24 13:59 Ong, Soo Keong
2006-04-24 14:13 ` Alan Cox
2006-04-24 14:15 Ong, Soo Keong
2006-04-24 14:29 ` Alan Cox
2006-05-03 20:25 ` Tim Small
2006-05-03 20:37 ` thockin
2006-05-04 9:45 ` Tim Small
2006-05-03 21:44 ` Alan Cox
2006-05-04 9:02 ` Tim Small
2006-04-24 14:32 Ong, Soo Keong
2006-04-24 15:57 Gross, Mark
2006-04-24 17:08 ` Eric W. Biederman
2006-04-24 17:49 ` Alan Cox
2006-04-24 18:14 Gross, Mark
2006-04-25 18:19 Gross, Mark
2006-04-25 19:55 ` Corey Minyard
2006-04-25 20:22 Gross, Mark
2006-04-25 21:24 Gross, Mark
2006-04-25 22:39 ` Corey Minyard
2006-04-25 23:25 Gross, Mark
2006-04-26 2:19 ` Corey Minyard
2006-04-26 2:34 ` Randy.Dunlap
2006-04-26 18:26 ` mark gross
2006-04-26 18:38 ` Randy.Dunlap
2006-04-26 19:39 ` mark gross
2006-04-26 20:17 ` Randy.Dunlap
2006-04-26 3:19 Gross, Mark
2006-04-26 3:24 Gross, Mark
2006-05-03 20:49 Gross, Mark
2006-05-03 21:39 Doug Thompson
2006-05-03 22:22 Doug Thompson
2006-05-03 23:06 David Peterson
2006-05-04 16:44 David Peterson
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=20060424173818.10362.qmail@web50103.mail.yahoo.com \
--to=norsk5@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=soo.keong.ong@intel.com \
--cc=steven.carbonari@intel.com \
--cc=zhenyu.z.wang@intel.com \
/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
all inboxes | Powered by JetHome®