From: "Jay Carlson" <nop@nop.com>
To: "Kevin D. Kissell" <kevink@mips.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
<Lisa.Hsu@taec.toshiba.com>
Cc: <linux-mips@oss.sgi.com>
Subject: RE: questions on the cross-compiler
Date: Fri, 5 Jan 2001 20:46:43 -0500 [thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNGEFGCAAA.nop@nop.com> (raw)
In-Reply-To: <006c01c07765$fdd26440$0deca8c0@Ulysses>
Kevin D. Kissell writes:
> Lisa's underlying problem may be that there isn't a Config
> option for the R39xx CPUs, and she's ended up getting an
> R4000 (or whatever) configuration by default.
>
> At some point specific support for the R3900 features
> (MIPS II ISA, seperate hardware interrupt vector, etc.)
> should go into the kernel,
[...]
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/linux/arch/mips/r39xx/?cvsroot
=linux-vr
The TX3912 is supported by the Linux VR kernel tree. I'm not sure it's been
tested in a while, but kernel sources from a few months ago run nice on my
VTech Helio.
Jay
WARNING: multiple messages have this Message-ID (diff)
From: "Jay Carlson" <nop@nop.com>
To: "Kevin D. Kissell" <kevink@mips.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Lisa.Hsu@taec.toshiba.com
Cc: linux-mips@oss.sgi.com
Subject: RE: questions on the cross-compiler
Date: Fri, 5 Jan 2001 20:46:43 -0500 [thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNGEFGCAAA.nop@nop.com> (raw)
Message-ID: <20010106014643.rTHAYDpB1TGfd5pTaKlRk24mOra02xSQeuZ6SSsF_c0@z> (raw)
In-Reply-To: <006c01c07765$fdd26440$0deca8c0@Ulysses>
Kevin D. Kissell writes:
> Lisa's underlying problem may be that there isn't a Config
> option for the R39xx CPUs, and she's ended up getting an
> R4000 (or whatever) configuration by default.
>
> At some point specific support for the R3900 features
> (MIPS II ISA, seperate hardware interrupt vector, etc.)
> should go into the kernel,
[...]
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/linux/arch/mips/r39xx/?cvsroot
=linux-vr
The TX3912 is supported by the Linux VR kernel tree. I'm not sure it's been
tested in a while, but kernel sources from a few months ago run nice on my
VTech Helio.
Jay
next prev parent reply other threads:[~2001-01-06 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 20:31 questions on the cross-compiler Lisa.Hsu
2001-01-05 20:52 ` Maciej W. Rozycki
2001-01-05 22:22 ` Kevin D. Kissell
2001-01-05 22:22 ` Kevin D. Kissell
2001-01-05 22:41 ` Maciej W. Rozycki
2001-01-06 1:46 ` Jay Carlson [this message]
2001-01-06 1:46 ` Jay Carlson
2001-01-07 15:33 ` Compiling MILO on big-emdian Michael Shmulevich
2001-01-07 19:05 ` Ralf Baechle
2001-01-08 8:04 ` Michael Shmulevich
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 1:44 questions on the cross-compiler Lisa.Hsu
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=KEEOIBGCMINLAHMMNDJNGEFGCAAA.nop@nop.com \
--to=nop@nop.com \
--cc=Lisa.Hsu@taec.toshiba.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.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