From: Ralf Baechle <ralf@linux-mips.org>
To: Jon Fraser <jfraser@broadcom.com>
Cc: Andrew Wiley <debio264@gmail.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: Bigsur?
Date: Mon, 18 May 2009 23:23:34 +0100 [thread overview]
Message-ID: <20090518222334.GD16847@linux-mips.org> (raw)
In-Reply-To: <1242663215.18301.26.camel@chaos.ne.broadcom.com>
On Mon, May 18, 2009 at 12:13:35PM -0400, Jon Fraser wrote:
> I think people that have them, have had them for a while.
>
> You can still get, I believe, the bcm91125 and bcm91250.
> http://www.broadcom.com/products/Data-Telecom-Networks/Communications-Processors/BCM91125E
> How you actually order one, I don't know. I assume you have to go to a
> distributor.
The usual story seems to be that people either turn pale when they hear
price on the order of $5,000 for a new board. Or they don't hear back
at all because a sole Linux hacker doesn't sound like he's going to buy
a few thousand chips every quarter.
Adjust the numbers a little (some go as high as $35,000 a board!) and they
apply to virtually every company.
> When I got a 1480 a year ago, it had to be built and took about 3
> months. The internal transfer cost was very high. So I really don't
> think they are available anymore. BUT, I don't work for that group.
>
> Are people just looking for eval type boards with MIPS cpus?
A clear yes. In particular the Swarm and Big Sur boards which aside of
graphics are as close to an workstation or server board, are highly
sought after as indicated by usually high 2nd hand prices on ebay.
Even though far from new these boards are the backbone of the native
compile farms of several Linux distributions including Debian and the
native testing by various commercial and non-commercial software
developers including myself. Aside of mostly SGI surplus workstations
the Sibyte boards are clearly the most popular among those who somehow
managed to get hold of them.
What this all boils down is that these aging platforms want a replacement
and a more accessible source. But for the time being they are still
the best for many developers.
Ralf
next prev parent reply other threads:[~2009-05-18 22:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 3:14 Bigsur? Andrew Wiley
2009-05-18 14:13 ` Bigsur? Ralf Baechle
2009-05-18 16:13 ` Bigsur? Jon Fraser
2009-05-18 16:31 ` Bigsur? David Daney
2009-05-18 17:23 ` Bigsur? Maciej W. Rozycki
2009-05-18 17:28 ` Bigsur? Markus Gothe
2009-05-18 19:02 ` Bigsur? Imre Kaloz
2009-05-18 19:37 ` Bigsur? Jon Fraser
2009-05-18 22:23 ` Ralf Baechle [this message]
2009-05-18 22:47 ` Bigsur? Maciej W. Rozycki
2009-05-19 12:17 ` Bigsur? Laurent GUERBY
2009-05-19 12:53 ` Bigsur? Ralf Baechle
2009-05-20 18:01 ` Bigsur? Andrew Sharp
2009-05-20 19:16 ` Bigsur? Ralf Baechle
2009-05-20 19:22 ` Bigsur? Manuel Lauss
2009-05-20 20:21 ` Bigsur? Laurent GUERBY
2009-05-20 23:17 ` Bigsur? Ralf Baechle
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=20090518222334.GD16847@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=debio264@gmail.com \
--cc=jfraser@broadcom.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.