linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Shane McDonald <mcdonald.shane@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>, linux-kernel@vger.kernel.org
Subject: Re: RM9000 / E9000, MSP71xx class processors, SOCs and eval boards
Date: Tue, 11 Dec 2012 12:14:28 +0100	[thread overview]
Message-ID: <20121211111427.GA23572@linux-mips.org> (raw)
In-Reply-To: <CACoURw7JTFMzmcRZHmBchcWPC8x5LFFfC1nGH-Xxc8f3KjNE2Q@mail.gmail.com>

On Thu, Dec 06, 2012 at 03:28:17PM -0600, Shane McDonald wrote:

> I'm interested in the MSP71xx eval board, although I may be
> the only person in the world who cares.  Specifically, I use the
> msp71xx_defconfig.  3.7-rc8 compiles with gcc-4.6.3
> without requiring any patches.
> 
> I don't know when the last time the RM9000 was compilable,
> but I have no interest in that, nor do I have interest in the
> FPGA or eval board versions of the MSP7120 (no hardware to
> test with).
> 
> I had hoped that someone from PMC-Sierra would respond, but
> maybe they don't care anymore...

Being a crazy tradition set by the Sparc AP1000, I'm happy with a single
user :-)

The Yosemite stuff scores higher on my kill list anyway.  The board
support code was never too great but that's not the issue; the SOC's
network driver which is rotting away in the linux-mips.org git tree as
the last change that can't be merged upstream as it is, stopped even
compiling ages ago and while a superior replacement has been posted,
nobody cared enough to get it into mergeable shape.

Now that 3.7 is finally released, hasta la vista, Yosemite.

  Ralf

      reply	other threads:[~2012-12-11 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 16:00 RM9000 / E9000, MSP71xx class processors, SOCs and eval boards Ralf Baechle
2012-12-06 21:28 ` Shane McDonald
2012-12-11 11:14   ` Ralf Baechle [this message]

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=20121211111427.GA23572@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mcdonald.shane@gmail.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;
as well as URLs for NNTP newsgroup(s).