Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: linux-mips@linux-mips.org
Subject: recommended toolchain
Date: Thu, 10 Apr 2003 12:23:19 -0700	[thread overview]
Message-ID: <20030410192319.GA21381@net-ronin.org> (raw)

Hi,

	What's the currently recommended toolchain for building MIPS kernels?
I'm working on a NEC VR4111 (mipsel, MIPS16, I, II, III, no LL/SC :P) and
would like to avoid tracking down toolchain bugs.

	Also, Are partial patches (i.e. platform not fully functional yet)
accepted?  Or should I finish a full port (hits userland) first?

	Vadem Clio 1000, reading the 2.4.0-test9 tree that's the last version
I see in CVS and porting to 2.5 (bk pull as of... a while ago).

	Thanks,

-- DN
Daniel

             reply	other threads:[~2003-04-10 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 19:23 carbonated beverage [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22  9:39 Recommended toolchain Phil Thompson
2001-03-22  9:43 ` Geert Uytterhoeven
2001-03-21 18:46 Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski
2001-03-22  7:49 ` Geert Uytterhoeven
2001-03-21 14:00 Phil Thompson
2001-03-21 12:11 ` Erik Mullinix
2001-03-21 16:06 ` Keith M Wesolowski
2001-03-20  3:06 Simon Gee
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:12   ` Karel van Houten
2001-03-20 20:37   ` Ralf Baechle
2001-03-20 20:37     ` Ralf Baechle
2001-03-27 19:02   ` Maciej W. Rozycki
2001-03-29 17:28     ` Houten K.H.C. van (Karel)
2001-03-29 17:28       ` Houten K.H.C. van (Karel)
2001-03-29 17:39       ` Karel van Houten
2001-03-29 17:39         ` Karel van Houten
2001-03-29 18:10         ` Maciej W. Rozycki
2001-04-01 14:39           ` Houten K.H.C. van (Karel)
2001-04-01 18:54             ` Florian Lohoff
2001-03-29 17:51       ` Maciej W. Rozycki

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=20030410192319.GA21381@net-ronin.org \
    --to=ramune@net-ronin.org \
    --cc=linux-mips@linux-mips.org \
    /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