From: Carsten Langgaard <carstenl@mips.com>
To: swang@mmc.atmel.com
Cc: linux-mips@oss.sgi.com
Subject: Re: Question on porting Linux...
Date: Wed, 22 Aug 2001 11:58:53 +0200 [thread overview]
Message-ID: <3B83825D.47619A46@mips.com> (raw)
In-Reply-To: 3B82D443.4C9DBDBE@mmc.atmel.com
You can find a kernel images for the SEAD board here:
ftp://ftp.mips.com/pub/linux/mips/kernel/2.4/images/vmlinux-2.4.3.sead.el-01.01.srec.gz
The sources are here:
ftp://ftp.mips.com/pub/linux/mips/kernel/2.4/src/linux-2.4.3.mips-src-01.01.tar.gz
To build your own ramdisk see Documentation/initrd.txt (in the sources) for how-to do it.
Put your ramdisk images in arch/mips/ramdisk/ramdisk.gz and compile the kernel (you can
use the .config.sead file for configure your kernel for the SEAD board, just copy it to
.config and then do 'make config').
Note that you need a other MIPS linux system to build your ramdisk.
Hope this is useful.
/Carsten
Shuanglin Wang wrote:
> > You are probably referring to the MIPS SEAD board, I have made a port for that board
> > now.
> > It runs with a small ramdisk, which basically only consist of a stand-alone shell
> > and a few simple commands like ls, etc...
> > So you can't do much with it, but you can make you own ramdisk, and just merge it in
> > with the kernel.
> > I will try to put an image on our FTP site
> > (ftp://ftp.mips.com/pub/linux/mips/kernel/2.4/images/) tomorrow.
> >
> > /Carsten
> >
>
> Yes, it is a MIPS SEAD-2 board. By the way, can I get the source code of the kernel
> with SEAD-2 board support ?
>
> >
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2001-08-22 10:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 1:30 Virtual address to physical address mapping machael thailer
2001-08-15 1:30 ` machael thailer
2001-08-15 8:33 ` Ralf Baechle
2001-08-20 9:54 ` questions about eret machael thailer
2001-08-20 9:54 ` machael thailer
2001-08-20 21:07 ` Ralf Baechle
2001-08-21 1:06 ` machael thailer
2001-08-21 1:06 ` machael thailer
2001-08-21 6:35 ` Ralf Baechle
2001-08-21 10:09 ` machael thailer
2001-08-21 10:09 ` machael thailer
2001-08-21 11:17 ` Ralf Baechle
2001-08-21 15:17 ` Question on porting Linux Shuanglin Wang
2001-08-21 14:33 ` jeff_lee
2001-08-21 14:33 ` jeff_lee
2001-08-21 15:33 ` Shuanglin Wang
2001-08-21 17:26 ` Jun Sun
2001-08-21 20:26 ` Carsten Langgaard
2001-08-21 21:36 ` Shuanglin Wang
2001-08-22 9:58 ` Carsten Langgaard [this message]
2001-08-21 1:34 ` questions about some bits of STATUS register and exception priority machael thailer
2001-08-21 1:34 ` machael thailer
2001-08-21 6:53 ` Ralf Baechle
2001-08-21 10:53 ` machael thailer
2001-08-21 10:53 ` machael thailer
2001-08-21 11:14 ` Ralf Baechle
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=3B83825D.47619A46@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=swang@mmc.atmel.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