Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Warner Losh <imp@village.org>
To: cypher <cypher@vertigo.cs.indiana.edu>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Wed, 03 Dec 1997 14:19:57 -0700	[thread overview]
Message-ID: <199712032119.OAA14390@harmony.village.org> (raw)
In-Reply-To: Your message of "Wed, 03 Dec 1997 13:31:09 EST." <Pine.LNX.3.95.971203132942.15095B-100000@vertigo.cs.indiana.edu>

In message <Pine.LNX.3.95.971203132942.15095B-100000@vertigo.cs.indiana.edu> cypher writes:
: There now exists an emulator for it. Now if one were to port the kernel to
: the emulator and then burn that to a rom.... hmmm

Hmmm.  Interesting.  How much does it cost to burn a EEPROM for the
N64?  I suspect the anser is $500 for the first one, and EEPROM cost +
$0.01 for each additional one due to startup costs.

Also, do you have a URL for the N64 emulator?

If memory serves, the N64 has a VR4700 chip in it made by IDT or some
such.  I have an IDT eval board that has a R4700 on it right now,
which would be enough to get Linux running on the chip.

But one does have to ask the question of WHY?  What can you get from
an N64 that would make it worth running Linux on it?

Warner

  reply	other threads:[~1997-12-03 21:25 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-02 21:50 Linux on the O2 cypher
1997-12-02 22:10 ` Ralf Baechle
1997-12-02 22:31   ` Ariel Faigon
1997-12-02 22:31     ` Ariel Faigon
1997-12-03  0:04     ` Alan Cox
1997-12-03  0:46       ` John Wiederhirn
1997-12-03  3:06         ` William J. Earl
1997-12-03  3:06           ` William J. Earl
1997-12-03 18:28         ` cypher
1997-12-03  1:51     ` Douglas F. Elznic
1997-12-03  1:51       ` Douglas F. Elznic
1997-12-03  7:01       ` ralf
     [not found]       ` <Pine.LNX.3.95.971203132942.15095B-100000@vertigo.cs.indian a.edu>
1997-12-03 18:04         ` Douglas F. Elznic
1997-12-03 18:39           ` Alan Cox
1997-12-03 18:39             ` Alan Cox
1997-12-03 18:42           ` cypher
1997-12-03 18:49           ` cypher
1997-12-03 18:05       ` David Chatterton
1997-12-03  2:34         ` Brendan Black
1997-12-03  2:58           ` Richard Offer
1997-12-03  3:19           ` Douglas F. Elznic
1997-12-03  8:21             ` Oliver Frommel
1997-12-03 10:51           ` Alan Cox
1997-12-03 10:51             ` Alan Cox
1997-12-03 18:32           ` cypher
1997-12-03 18:31       ` cypher
1997-12-03 21:19         ` Warner Losh [this message]
1997-12-03 22:16           ` Chad Campbell
1997-12-03 22:31             ` William J. Earl
1997-12-03 22:48               ` Alan Cox
1997-12-03 22:48                 ` Alan Cox
     [not found]           ` <Pine.LNX.3.95.971203161250.15277A-100000@dv123s34.lawrence .ks.us>
1997-12-03 22:38             ` Douglas F. Elznic
1997-12-02 22:33   ` William J. Earl
1997-12-02 23:32     ` Christian Reisch
1997-12-02 23:45       ` William J. Earl
1997-12-03  0:09 ` Alan Cox
1997-12-03  0:09   ` Alan Cox
1997-12-03  7:46 ` Chris Carlson
1997-12-04  5:39   ` Lige Hensley
1997-12-04  5:39     ` Lige Hensley
1997-12-04  5:48     ` David S. Miller
1997-12-04 16:55       ` Greg Chesson
1997-12-04 16:51     ` Greg Chesson
1997-12-04 22:08     ` David Chatterton
1997-12-04 14:06       ` Lige Hensley
1997-12-04 17:03       ` Greg Chesson
1997-12-04 17:22         ` William J. Earl
1997-12-04 18:59           ` Alan Cox
1997-12-04 18:59             ` Alan Cox
1997-12-04 22:01           ` ralf
1997-12-04 23:33             ` William J. Earl
1997-12-05  1:33               ` ralf
1997-12-05  3:25                 ` Chad Campbell
1997-12-04 18:54         ` Alan Cox
1997-12-04 18:54           ` Alan Cox
1997-12-04 19:41           ` Alex deVries
1997-12-04 22:28             ` Eric Kimminau
1997-12-04 22:44               ` Alan Cox
1997-12-05  0:17           ` ralf
1997-12-05  9:06             ` Alan Cox

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=199712032119.OAA14390@harmony.village.org \
    --to=imp@village.org \
    --cc=cypher@vertigo.cs.indiana.edu \
    --cc=linux@cthulhu.engr.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