linux-mips
[Top] [All Lists]

RE: [PATCH 01/10] MIPS: Add core files for MIPS SEAD-3 development platf

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: RE: [PATCH 01/10] MIPS: Add core files for MIPS SEAD-3 development platform.
From: "Hill, Steven" <sjhill@mips.com>
Date: Tue, 8 May 2012 20:38:12 +0000
Accept-language: en-US
Cc: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>, "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>, "ralf@linux-mips.org" <ralf@linux-mips.org>
In-reply-to: <alpine.LFD.2.00.1205080945120.3701@eddie.linux-mips.org>
References: <1333817315-30091-1-git-send-email-sjhill@mips.com> <1333817315-30091-2-git-send-email-sjhill@mips.com>,<4F8386C8.9020401@renesas.com> <31E06A9FC96CEC488B43B19E2957C1B8011469208F@exchdb03.mips.com>,<alpine.LFD.2.00.1205080945120.3701@eddie.linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
Thread-index: AQHNFN5TXaIyKURn50SCHT0BxYKwcJaTtvkAgCs4fmCAAXRPAIAAJgYC
Thread-topic: [PATCH 01/10] MIPS: Add core files for MIPS SEAD-3 development platform.
I thought the "YC" constraint was only present in CodeSourcery toolchains, 
correct? If so, then that levies the requirement for a vendor-specific 
toolchain to build a microMIPS kernel. I do not consider that palpable. If it 
is not CodeSourcery-specific, then I will certainly try it out.

<Prev in Thread] Current Thread [Next in Thread>