From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: anyone using Itanium B-step support?
Date: Thu, 27 Jan 2005 22:12:55 +0000 [thread overview]
Message-ID: <16889.26471.787124.55865@napali.hpl.hp.com> (raw)
In-Reply-To: <1106862995.18514.108.camel@aretha.corp.specifixinc.com>
>>>>> On Thu, 27 Jan 2005 13:56:36 -0800, James E Wilson <wilson@specifixinc.com> said:
Jim> However, rather than add more ITANIUM_BSTEP_SPECIFIC support to
Jim> the kernel, I think it makes more sense to obsolete it and
Jim> remove it.
I agree. I happened to run into the warning just recently myself and
came to the same conclusion.
We probably still have some B-step Merceds in our lab but IIRC, it was
so rare to trigger the erratum that even on those boxes we can live
without the workaround just fine. And it's not likely that anyone is
using such old prototype hardware for anything mission critical...
--david
next prev parent reply other threads:[~2005-01-27 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:56 anyone using Itanium B-step support? James E Wilson
2005-01-27 22:12 ` David Mosberger [this message]
2005-01-28 1:24 ` James E Wilson
2005-01-28 1:54 ` David Mosberger
2005-01-28 2:32 ` James E Wilson
2005-01-28 6:17 ` David Mosberger
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=16889.26471.787124.55865@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox