| To: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
|---|---|
| Subject: | Re: Porting To New System |
| From: | Cameron Cooper <developer@phatlinux.com> |
| Date: | Fri, 27 May 2005 15:52:19 -0400 |
| Cc: | Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>, linux-mips@linux-mips.org |
| In-reply-to: | <1117217584.5743.229.camel@localhost.localdomain> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <Pine.GSO.4.10.10505271929510.25076-100000@helios.et.put.poznan.pl> <1117217584.5743.229.camel@localhost.localdomain> |
| Sender: | linux-mips-bounce@linux-mips.org |
> 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. I've looked into using uClinux, and although it appears as though it does support MIPS, it is very hard to find any information on it. Do you have any information regarding using uClinux with MIPS? Thanks, Cameron Cooper |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Porting To New System, Stanislaw Skowronek |
|---|---|
| Next by Date: | Re: Porting To New System, Alan Cox |
| Previous by Thread: | Re: Porting To New System, Cameron Cooper |
| Next by Thread: | Re: Porting To New System, Alan Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |