Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Cameron Cooper <developer@phatlinux.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>,
	linux-mips@linux-mips.org
Subject: Re: Porting To New System
Date: Fri, 27 May 2005 14:21:15 -0400	[thread overview]
Message-ID: <1117218075.2921.2.camel@phatbox> (raw)
In-Reply-To: <1117217584.5743.229.camel@localhost.localdomain>

> For ucLinux you essentially need a console, an input device (keyboard
> etc), a storage device, the ability to allocate memory and a timer
> interrupt/callback. Absolutely everything else is optional. So you can
> probably run ucLinux as a 'game' which allocates lots of memory,
> requests a timer callback and drives the entire world through the
> firmware. Whether you can do non-ucLinux depends on MMU access and
> control. If you've got some kind of MMU interface then you've probably
> got sufficient to do a full Linux but ucLinux would still be a natural
> stepping stone in exploration.

Thank you, that is a very useful bit of information. I will start with
ucLinux. Once (if?) a MMU interface is discovered then I will do a full
Linux kernel.

Cameron

  reply	other threads:[~2005-05-27 18:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 16:59 Porting To New System Cameron Cooper
2005-05-27 17:30 ` Stanislaw Skowronek
2005-05-27 18:13   ` Alan Cox
2005-05-27 18:21     ` Cameron Cooper [this message]
2005-05-27 19:43       ` Stanislaw Skowronek
2005-05-27 23:12         ` Alan Cox
2005-05-28  5:07           ` Stanislaw Skowronek
2005-05-28  7:30           ` Stanislaw Skowronek
2005-05-28 15:48             ` Cameron Cooper
2005-05-27 19:52     ` Cameron Cooper
2005-05-27 23:40       ` Alan Cox
2005-05-28 15:43         ` Cameron Cooper
2005-05-28 19:27           ` Ralf Baechle
2005-05-28 19:35             ` Cameron Cooper
  -- strict thread matches above, loose matches on Subject: below --
2005-05-27 16:28 Cameron Cooper
2005-05-27 16:41 ` Alan Cox
2005-05-27  3:11 developer
2005-05-27  4:37 ` Stanislaw Skowronek
2005-05-27  5:13 ` Ed Okerson
2005-05-27  5:40   ` Stanislaw Skowronek
2005-05-27  6:22     ` Kumba
2005-05-27 22:51 ` Ralf Baechle
2005-05-28 19:43   ` Cameron Cooper
2005-05-28 19:50     ` Thiemo Seufer
2005-05-28 19:55     ` Ralf Baechle
2005-05-28 19:55       ` Cameron Cooper

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=1117218075.2921.2.camel@phatbox \
    --to=developer@phatlinux.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=sskowron@ET.PUT.Poznan.PL \
    /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