Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mike McDonald <mikemac@mikemac.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Embedded MIPS/Linux Needs
Date: Thu, 22 Mar 2001 06:17:28 -0800	[thread overview]
Message-ID: <200103221417.GAA20495@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Thu, 22 Mar 2001 12:48:19 +0100." <00eb01c0b2c6$02c7ef60$0deca8c0@Ulysses>


>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

>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"?

  A bootloader that runs under WinCE 3.0!

  Mike McDonald
  mikemac@mikemac.com

  parent reply	other threads:[~2001-03-22 14:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 11:48 Embedded MIPS/Linux Needs Kevin D. Kissell
2001-03-22 11:48 ` 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 [this message]
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=200103221417.GAA20495@saturn.mikemac.com \
    --to=mikemac@mikemac.com \
    --cc=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