From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
Carlos O'Donell <carlos@systemhalted.org>,
linux-parisc@vger.kernel.org
Subject: Re: False advertising (was: C8000 cpu upgrade problem)
Date: Sat, 23 Oct 2010 15:29:37 -0500 [thread overview]
Message-ID: <1287865777.3003.31.camel@mulgrave.site> (raw)
In-Reply-To: <20101023194212.GA23609@hiauly1.hia.nrc.ca>
On Sat, 2010-10-23 at 15:42 -0400, John David Anglin wrote:
> > But it seems that people on this list don't know about those HP locks too
> > :-(
>
> Most don't have any affiliation with HP. I have been on this list a
> long time, and don't believe this issue has been discussed before,
> although the kernel maintainers may be aware of it.
>
> In general, this kind of hardware information is proprietory. The
> PC architecture only opened up because of a lot of competition and
> reverse engineering. Even there, you may need a NDA to access some
> documentation. It costs $3000/year to access PCI-SIG documents, etc.
>
> James, what kind of firmware update is needed?
I have no idea ... I'm only deducing this from what had to be done to
ion to make it a 4-way. We had similar upgrades to some of the A180s as
well. It is unusual for a workstation class system, but the "too many
CPUs" message seems definitive. Perhaps the firmware is essentially the
same as a server class and it's inheriting this behaviour.
James
next prev parent reply other threads:[~2010-10-23 20:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:07 C8000 cpu upgrade problem Mikulas Patocka
2010-10-22 18:09 ` Carlos O'Donell
2010-10-23 9:21 ` Mikulas Patocka
2010-10-23 11:22 ` Carlos O'Donell
2010-10-23 14:46 ` False advertising (was: C8000 cpu upgrade problem) Mikulas Patocka
2010-10-23 16:57 ` James Bottomley
2010-10-23 17:14 ` Matt Turner
2010-10-24 1:18 ` Thibaut VARÈNE
2010-10-24 1:50 ` Matt Turner
2010-10-24 3:18 ` Mikulas Patocka
2010-10-24 11:36 ` Thibaut VARÈNE
2010-10-23 18:20 ` Mikulas Patocka
2010-10-23 19:42 ` John David Anglin
2010-10-23 19:58 ` Kyle McMartin
2010-10-23 23:45 ` Mikulas Patocka
2010-10-23 20:29 ` James Bottomley [this message]
2010-10-23 21:50 ` John David Anglin
2010-10-23 15:25 ` C8000 cpu upgrade problem Matt Turner
2010-10-23 16:40 ` Mikulas Patocka
2010-10-23 15:47 ` John David Anglin
2010-10-23 16:02 ` Mikulas Patocka
2010-10-23 17:41 ` John David Anglin
2010-10-23 17:53 ` Mikulas Patocka
2010-10-23 18:11 ` John David Anglin
2010-10-23 18:33 ` Mikulas Patocka
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=1287865777.3003.31.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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