Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mark Mason <mmason@upwardaccess.com>
To: linux-mips@linux-mips.org
Subject: Re: FW: Bigsur?
Date: Mon, 01 Jun 2009 12:03:03 -0700	[thread overview]
Message-ID: <1243882983.3841.5.camel@hawaii.site> (raw)
In-Reply-To: <BD3F7F1EFBA6D54DB056C4FFA4514008035D800690@SJEXCHCCR01.corp.ad.broadcom.com>

On Wednesday, May 20, 2009 12:16 PM, Ralf Baechle wrote:
> 
> For many uses that will be decent but there are still a few things out
> there that don't quite work the same way on NFS that they do on other
> filesystems and that tends to break some software and autoconf-like
> things.  I'd probably give such a config a 90% score - good for most stuff.
> 

Unfortunately, we didn't get as many of the bigsur machines out there as
I would have liked before the Sibyte product was deprecated. Perhaps
over time, as space is made in the labs for new projects, more of the
1250 and 1480 boards will become available.

Mark

           reply	other threads:[~2009-06-01 18:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BD3F7F1EFBA6D54DB056C4FFA4514008035D800690@SJEXCHCCR01.corp.ad.broadcom.com>]

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=1243882983.3841.5.camel@hawaii.site \
    --to=mmason@upwardaccess.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox