Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: <linux-mips@oss.sgi.com>
Subject: Embedded MIPS/Linux Needs
Date: Thu, 22 Mar 2001 12:48:19 +0100	[thread overview]
Message-ID: <00eb01c0b2c6$02c7ef60$0deca8c0@Ulysses> (raw)

Here at MIPS Technologies, we use Linux internally
for design verification, experiments, benchmarking,
etc., and as a consequence Carsten Langgaard and
myself have both been active in this forum, and have
tried to help the general Linux/MIPS community as
best we can with the limited time that we can dedicate
to the problem, in terms of suggested patches, bug
fixes, cleanups, integration of needed components
like the FPU emulator, etc.

I have a question for those of you who are doing
Linux work for *new* platforms (as opposed to the
SGI/DEC legacy box support people).  IF, and I
emphasize the word *if*, MIPS Technologies were
make a bigger investment in MIPS/Linux technology,
be it kernel enhancements, cross/native tools,
userland ports, libraries, or whatever, what would
be your prioritized "wish list"?

Feel free to respond by point-to-point email, though
responses that are also copied to the mailing list
might provoke some interesting and enlightening
debate.

            Regards,

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: linux-mips@oss.sgi.com
Subject: Embedded MIPS/Linux Needs
Date: Thu, 22 Mar 2001 12:48:19 +0100	[thread overview]
Message-ID: <00eb01c0b2c6$02c7ef60$0deca8c0@Ulysses> (raw)
Message-ID: <20010322114819.2hr7-kX8s9C0CJCZndwxYGV8GSUQ_RyTeyCVBWFrn50@z> (raw)

Here at MIPS Technologies, we use Linux internally
for design verification, experiments, benchmarking,
etc., and as a consequence Carsten Langgaard and
myself have both been active in this forum, and have
tried to help the general Linux/MIPS community as
best we can with the limited time that we can dedicate
to the problem, in terms of suggested patches, bug
fixes, cleanups, integration of needed components
like the FPU emulator, etc.

I have a question for those of you who are doing
Linux work for *new* platforms (as opposed to the
SGI/DEC legacy box support people).  IF, and I
emphasize the word *if*, MIPS Technologies were
make a bigger investment in MIPS/Linux technology,
be it kernel enhancements, cross/native tools,
userland ports, libraries, or whatever, what would
be your prioritized "wish list"?

Feel free to respond by point-to-point email, though
responses that are also copied to the mailing list
might provoke some interesting and enlightening
debate.

            Regards,

            Kevin K.

             reply	other threads:[~2001-03-22 11:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 11:48 Kevin D. Kissell [this message]
2001-03-22 11:48 ` Embedded MIPS/Linux Needs Kevin D. Kissell
2001-03-22 14:01 ` Jay Carlson
2001-03-22 14:01   ` Jay Carlson
2001-03-22 18:32   ` Jun Sun
2001-03-22 14:17 ` Mike McDonald
2001-03-22 18:23 ` Jeff Harrell
2001-03-22 18:23   ` Jeff Harrell
2001-03-26  3:01 ` Joe deBlaquiere
2001-03-26  3:23   ` Keith Owens
2001-03-26  4:06   ` Keith M Wesolowski
2001-03-26 17:25   ` Florian Lohoff
2001-03-26 18:47     ` Joe deBlaquiere
2001-03-26 23:24       ` Jun Sun
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22 12:27 Phil Thompson
2001-03-22 19:02 Justin Carlson
2001-03-22 19:03 ` nick
2001-03-22 19:22   ` Keith M Wesolowski

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='00eb01c0b2c6$02c7ef60$0deca8c0@Ulysses' \
    --to=kevink@mips.com \
    --cc=linux-mips@oss.sgi.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