From: Ralf Baechle <ralf@linux-mips.org>
To: shiraz.ta@philips.com
Cc: linux-mips@linux-mips.org
Subject: Re: Porting of Linux on to a MIPS16 Processor. Help required
Date: Fri, 14 May 2004 14:11:58 +0200 [thread overview]
Message-ID: <20040514121158.GA5466@linux-mips.org> (raw)
In-Reply-To: <OF9C1094DD.6309A695-ON45256E94.002F4A91-65256E94.00311FA8@philips.com>
On Fri, May 14, 2004 at 02:24:50PM +0530, shiraz.ta@philips.com wrote:
> I am new to linux. I am in need of porting linux to a MIPS16 based
> processor. I need some information regarding the porting. It will be a
> great help if somebody could answer me.
>
> 1) Is there any port available already for this? If available how do i get
> it along with the development environment.
>
> 2) If the port is not available then how much complex (How much effort ?)
> is it to port it to MIPS 16.
>
> 3) Where can I get the tool chain on windows and linux kernel source code
> which can be used .
You forgot to mention the exact processor type but anyway, MIPS16 is
really just an extension. As such Linux can run on a system without
actually knowing anything about MIPS16. Which is nice, if you intend to
actually exploit MIPS16 you don't have to have that working right away but
can introduce support later, as optimization for size.
Windows? Good luck. I've seen success reports with Cygwin but if you want
to keep things sane, use a Linux box for development.
> 6) I would like to know how much would be the code size for the kernel
> alone with out any shell and with the console driver. (Source code and
> Binary)
To my knowledge nobody has used MIPS16 for Linux so far. There seems
little point in that because MIPS16 primarily targets very small systems -
a class of systems that Linux doesn't tend to run on well.
Ralf
prev parent reply other threads:[~2004-05-14 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 8:54 Porting of Linux on to a MIPS16 Processor. Help required shiraz.ta
2004-05-14 12:11 ` Ralf Baechle [this message]
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=20040514121158.GA5466@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=shiraz.ta@philips.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