From: Ralf Baechle <ralf@linux-mips.org>
To: Bryan Althouse <bryan.althouse@3phoenix.com>
Cc: "'Alex Gonzalez'" <linux-mips@packetvision.com>,
linux-mips@linux-mips.org
Subject: Re:
Date: Wed, 4 May 2005 17:42:27 +0100 [thread overview]
Message-ID: <20050504164227.GE5525@linux-mips.org> (raw)
In-Reply-To: <20050504142226Z8225804-1340+6519@linux-mips.org>
On Wed, May 04, 2005 at 10:22:08AM -0400, Bryan Althouse wrote:
> Thanks for your help. Yes I do need SMP. Jason Liu of PMC did a check on
> my serial number, and found that I have rev 1.1 silicon. He says I need rev
> 1.2 in order to use a 2.6.x kernel. I have shipped my hardware back to them
> for an upgrade. Hopefully, I'll be back in business in a week or two.
That is correct. Earlier revisions didn't implement some functionality
that is crucial to SMP. Since only PMC and a small number outside parties
have pre-1.2 silicon I agreed with PMC to not try to support earlier
revisions.
Ralf
next prev parent reply other threads:[~2005-05-04 16:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 19:15 Bryan Althouse
2005-04-28 19:15 ` Bryan Althouse
2005-04-29 11:02 ` your mail Ralf Baechle
2005-04-29 13:52 ` your mail (yosemite + 2.6.x issues) Bryan Althouse
2005-04-29 13:52 ` Bryan Althouse
2005-04-29 16:08 ` Manish Lachwani
2005-05-04 14:05 ` Alex Gonzalez
2005-05-04 13:55 ` Alex Gonzalez
2005-05-04 14:22 ` Bryan Althouse
2005-05-04 14:22 ` RE: Bryan Althouse
2005-05-04 16:42 ` Ralf Baechle [this message]
2005-05-05 14:55 ` Ralf Baechle
2005-05-05 15:08 ` Bryan Althouse
2005-05-05 15:08 ` RE: Bryan Althouse
2005-05-05 15:11 ` Ralf Baechle
2005-05-05 15:57 ` Re: Geert Uytterhoeven
2005-05-05 17:13 ` Re: Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 9:09 Paulo Miguel Almeida
2024-10-17 9:12 ` Paulo Miguel Almeida
2020-05-06 5:52 Jiaxun Yang
2020-05-06 17:17 ` Nick Desaulniers
2017-11-13 14:55 Re: Amos Kalonzo
2017-11-13 14:55 ` Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2017-02-23 15:09 ` RE: Qin's Yanjun
2010-06-11 14:06 Jabir M
2010-06-11 14:32 ` Manuel Lauss
2010-06-11 17:06 ` Re: David Daney
2010-06-11 17:33 ` Re: Kevin D. Kissell
2010-06-11 18:28 ` Re: Manuel Lauss
2006-01-04 12:50 Sathesh Babu Edara
2006-01-04 13:06 ` Kevin D. Kissell
2006-01-09 7:43 ` Sathesh Babu Edara
2006-01-09 7:43 ` RE: Sathesh Babu Edara
2006-01-09 9:00 ` Kevin D. Kissell
2006-01-09 9:00 ` Re: Kevin D. Kissell
2005-04-28 21:30 Raj Palani
2004-11-16 6:09 Fuxin Zhang
2004-11-14 1:32 Re: Fuxin Zhang
2004-11-13 14:47 Re: macrohat
2004-09-03 8:57 xuhaoz
2004-09-03 21:47 ` Fuxin Zhang
2004-08-27 1:49 Re: bel racu
2004-04-14 6:05 caoxiang
2004-04-14 18:34 ` Fuxin Zhang
2003-11-01 1:38 Lyle Bainbridge
2003-11-03 18:14 ` Pete Popov
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=20050504164227.GE5525@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bryan.althouse@3phoenix.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@packetvision.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