From: "David Christensen" <dpchrist@holgerdanske.com>
To: <linux-mips@oss.sgi.com>
Cc: "Domcan Sami" <domca_psg@email.com>
Subject: Re: Kernel - arch support(mips)
Date: Fri, 14 Jun 2002 11:15:35 -0700 [thread overview]
Message-ID: <00a601c213cf$8bf56b30$0b01a8c0@w2k30g> (raw)
In-Reply-To: 20020614115049.16384.qmail@email.com
linux-mips@oss.sgi.com:
Domcan Sami <domca_psg@email.com> wrote:
> I am trying to compile a program using a MIPS-LINUX cross compiler
> (gcc). I've set up a connection between my i386 Linux machine and a
> MIPS(RM7000) processor. This is again connected to a WinNT Terminal
> where there should be an output from the MIPS processor.
>
> I have 2 kernels in my Linux machine under the directories:
> 1) /usr/src/linux - kernel version 2.2.14
> 2) /root/kernels/linux - kernel version 2.4.14
>
> I am using a boot image generated from the older kernel for booting.
> The problem is the older kernel doesn't support MIPS architecture.
> What should I do to upgrade my kernel so that it supports MIPS
> architecture & that I'll be able to cross-compile my programs
> properly.
Please provide more information:
1. What is your target platform -- e.g. make of model of the board or
computer that has the RM7000 processor on/in it?
2. Does the target support Linux, does it have a ROM monitor, or is it
a raw embedded target (e.g. requires crt0)?
David Christensen
dpchrist@holgerdanske.com
WARNING: multiple messages have this Message-ID (diff)
From: "David Christensen" <dpchrist@holgerdanske.com>
To: linux-mips@oss.sgi.com
Cc: Domcan Sami <domca_psg@email.com>
Subject: Re: Kernel - arch support(mips)
Date: Fri, 14 Jun 2002 11:15:35 -0700 [thread overview]
Message-ID: <00a601c213cf$8bf56b30$0b01a8c0@w2k30g> (raw)
Message-ID: <20020614181535.bh7icH_KB99wSF_eaRKz4UE3kteV1tPDaYCTd8k4YNY@z> (raw)
In-Reply-To: 20020614115049.16384.qmail@email.com
linux-mips@oss.sgi.com:
Domcan Sami <domca_psg@email.com> wrote:
> I am trying to compile a program using a MIPS-LINUX cross compiler
> (gcc). I've set up a connection between my i386 Linux machine and a
> MIPS(RM7000) processor. This is again connected to a WinNT Terminal
> where there should be an output from the MIPS processor.
>
> I have 2 kernels in my Linux machine under the directories:
> 1) /usr/src/linux - kernel version 2.2.14
> 2) /root/kernels/linux - kernel version 2.4.14
>
> I am using a boot image generated from the older kernel for booting.
> The problem is the older kernel doesn't support MIPS architecture.
> What should I do to upgrade my kernel so that it supports MIPS
> architecture & that I'll be able to cross-compile my programs
> properly.
Please provide more information:
1. What is your target platform -- e.g. make of model of the board or
computer that has the RM7000 processor on/in it?
2. Does the target support Linux, does it have a ROM monitor, or is it
a raw embedded target (e.g. requires crt0)?
David Christensen
dpchrist@holgerdanske.com
next prev parent reply other threads:[~2002-06-15 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 11:50 Kernel - arch support(mips) Domcan Sami
2002-06-14 18:15 ` David Christensen [this message]
2002-06-14 18:15 ` David Christensen
[not found] <20020615091631.20470.qmail@email.com>
2002-06-15 21:16 ` David Christensen
2002-06-15 21:16 ` David Christensen
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='00a601c213cf$8bf56b30$0b01a8c0@w2k30g' \
--to=dpchrist@holgerdanske.com \
--cc=domca_psg@email.com \
--cc=linux-mips@oss.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