From: Craig Milo Rogers <rogers@isi.edu>
To: "Theodore Ts'o" <tytso@mit.edu>, "H. Peter Anvin" <hpa@zytor.com>,
Brian Gerst <brgerst@gmail.com>, wbrana <wbrana@gmail.com>,
Martin Nybo Andersen <tweek@tweek.dk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Space-Certified CPUs and Linux
Date: Fri, 24 Aug 2012 13:18:46 -0700 [thread overview]
Message-ID: <20120824201846.GA11418@isi.edu> (raw)
In-Reply-To: <20120824185741.GC5094@thunk.org>
On 12.08.24, Theodore Ts'o wrote:
> Random question. As I recall the Space Shuttle and the International
> Space Station was only using 80386's because they have to be hardened
> against radiation/cosmic rays, as well as all of the other mechnical
> and thermal stresses associated with being in a spacecraft. Is there
> any newer generation cpu's which are space-cerified at this point?
The MAESTRO processor is a rad-hard-by-design variant of the Tilera
architecture, intended for space applications. Linux runs on it.
The Mongoose-V is a rad-hard MIPS R3000 processor. It can run
VxWorks, made by Wind River (a subsidiary of Intel since 2009).
http://www.synova.com/proc/mg5.html
Rad-hard Power PCs are the current space workhorse. Several variants
are available. NASA has run Linux on at least one of them in space, but I
believe that VxWorks is more the norm.
> (Of course, I'm rather doubtful that NASA would ever be willing to use
> Linux on something like the Curiosity Mars Rover, but I could imagine
> Linux being used in a non-mission critcal system on the ISS....)
Linux has been use on scientific equipment sent to the ISS.
Not, I think, on the avionics.
Curiosity runs VxWorks, as do the SpaceX Falcon 9 and Dragon.
Craig Milo Rogers
next prev parent reply other threads:[~2012-08-24 20:39 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 10:41 Drop support for x86-32 wbrana
[not found] ` <201208231814.21168.tweek@tweek.dk>
2012-08-23 17:22 ` wbrana
2012-08-23 17:51 ` Ondrej Zary
2012-08-23 18:07 ` wbrana
2012-08-24 12:40 ` Bernd Petrovitsch
2012-08-24 12:59 ` wbrana
2012-08-24 13:51 ` wbrana
2012-08-24 15:48 ` Bernd Petrovitsch
2012-08-24 15:55 ` wbrana
[not found] ` <CANQmPXj6VsxP596xeU5SZaL=eyDJR4_ShBxCJVqthYTdNA4HSw@mail.gmail.com>
2012-08-24 16:11 ` wbrana
2012-08-24 16:14 ` Martin Nybo Andersen
2012-08-24 16:17 ` wbrana
2012-08-24 16:20 ` Bobby Powers
2012-08-24 16:24 ` wbrana
2012-08-24 16:20 ` Martin Nybo Andersen
2012-08-24 16:26 ` wbrana
[not found] ` <201208241832.09577.tweek@tweek.dk>
2012-08-24 16:39 ` wbrana
2012-08-24 16:24 ` Chris Friesen
2012-08-24 16:54 ` Martin Nybo Andersen
2012-08-24 17:05 ` wbrana
2012-08-24 17:25 ` Chris Friesen
2012-08-24 17:28 ` Brian Gerst
2012-08-24 18:11 ` Gene Heskett
[not found] ` <201208241952.04988.tweek@tweek.dk>
2012-08-24 18:18 ` wbrana
2012-08-24 18:35 ` Martin Nybo Andersen
2012-08-24 18:59 ` wbrana
2012-08-24 19:53 ` Martin Nybo Andersen
2012-08-25 8:27 ` wbrana
2012-08-25 8:43 ` Gene Heskett
2012-08-25 9:25 ` wbrana
2012-08-25 12:20 ` wbrana
2012-08-25 14:41 ` wbrana
2012-08-25 15:51 ` Shentino
2012-08-25 16:07 ` wbrana
2012-08-25 11:35 ` Bernd Petrovitsch
2012-08-25 11:52 ` wbrana
2012-08-25 16:46 ` Jochen Striepe
2012-08-25 17:22 ` wbrana
2012-08-25 17:24 ` Shentino
2012-08-25 17:27 ` wbrana
2012-08-25 17:34 ` Pekka Enberg
2012-08-25 17:38 ` wbrana
2012-08-26 2:18 ` Henrique de Moraes Holschuh
2012-08-26 2:30 ` Cruz Julian Bishop
2012-08-27 12:21 ` Bernd Petrovitsch
2012-08-25 17:40 ` Jochen Striepe
2012-08-25 17:49 ` wbrana
2012-08-25 0:51 ` Cruz Julian Bishop
2012-08-25 7:46 ` wbrana
[not found] ` <CANQmPXgefyCJuzFiAugp6OW2+HtjABSWuQqG33gAU_XgQ1V_2A@mail.gmail.com>
2012-08-24 16:19 ` wbrana
2012-08-24 16:36 ` Alan Cox
2012-08-24 16:36 ` wbrana
2012-08-24 16:47 ` Alan Cox
2012-08-24 16:45 ` wbrana
2012-08-26 13:56 ` Mark Lord
[not found] ` <CAJ7jCm=A+OOQNq3HYsyM9bVXYQbfxkXaJg+yN_-vyA+VM9-jgQ@mail.gmail.com>
2012-08-29 23:03 ` Mark Lord
2012-08-29 23:42 ` Jeff Garzik
2012-08-25 0:57 ` Cruz Julian Bishop
2012-08-23 18:08 ` Al Viro
2012-08-23 18:17 ` wbrana
2012-08-23 18:22 ` Pekka Enberg
2012-08-23 18:23 ` David Daney
2012-08-23 18:30 ` wbrana
2012-08-23 18:33 ` David Daney
2012-08-23 18:40 ` wbrana
2012-08-23 19:01 ` Al Viro
2012-08-24 9:51 ` wbrana
2012-08-23 18:50 ` Martin Nybo Andersen
2012-08-23 18:54 ` Brian Gerst
2012-08-23 19:03 ` wbrana
2012-08-23 19:04 ` Brian Gerst
2012-08-23 19:08 ` wbrana
2012-08-23 19:35 ` Brian Gerst
2012-08-24 9:50 ` wbrana
2012-08-24 10:27 ` Ronnie Collinson
2012-08-24 10:30 ` wbrana
2012-08-24 10:36 ` wbrana
2012-08-24 10:38 ` Ronnie Collinson
2012-08-24 10:42 ` wbrana
2012-08-24 10:49 ` Maarten Lankhorst
2012-08-24 10:59 ` Ronnie Collinson
2012-08-24 11:57 ` Brian Gerst
2012-08-24 9:53 ` wbrana
2012-08-24 12:00 ` Brian Gerst
2012-08-24 12:04 ` wbrana
2012-08-24 12:14 ` Ondrej Zary
2012-08-24 12:27 ` wbrana
2012-08-24 18:17 ` H. Peter Anvin
2012-08-24 18:57 ` Theodore Ts'o
2012-08-24 19:13 ` Alan Cox
2012-08-24 19:58 ` Theodore Ts'o
2012-08-24 20:06 ` Dave Jones
2012-08-24 20:25 ` Borislav Petkov
2012-08-24 20:47 ` H. Peter Anvin
2012-08-24 19:38 ` H. Peter Anvin
2012-08-24 19:40 ` H. Peter Anvin
2012-08-24 20:18 ` Craig Milo Rogers [this message]
2012-08-24 20:49 ` Sam Ravnborg
2012-08-30 1:14 ` david
2012-08-24 16:24 ` Raymond Jennings
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=20120824201846.GA11418@isi.edu \
--to=rogers@isi.edu \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tweek@tweek.dk \
--cc=tytso@mit.edu \
--cc=wbrana@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
Powered by JetHome