From: Bryan Hundven <bryanhundven@gmail.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: M P <buserror@gmail.com>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: cavium support
Date: Fri, 12 Dec 2014 20:38:00 -0000 [thread overview]
Message-ID: <CAJ+oik0ofoBuP=qT8==B15aW41ve0bbV2e9ygVsB3U7zUdH3Rw@mail.gmail.com> (raw)
In-Reply-To: <CAAA5faFABohqrqYpGJbMoTnDzPNaPjZYVE=aitGuEowuKiSq=w@mail.gmail.com>
Reinoud,
On Thu, Dec 11, 2014 at 1:13 AM, Reinoud Koornstra
<reinoudkoornstra@gmail.com> wrote:
> Well, when choosing the cpu type, cavium is not in the list of support cpu's.
> Do you mean you set the cpu to mips 32 bits of 64 bits to support these cpu's?
> Have you been building it in combination with uclibc or glibc?
> Thanks,
>
> Reinoud.
>
> On Thu, Dec 11, 2014 at 1:43 AM, M P <buserror@gmail.com> wrote:
>> On 9 December 2014 at 22:03, Bryan Hundven <bryanhundven@gmail.com> wrote:
>>>
>>> Reinoud,
>>>
>>> On Tue, Dec 9, 2014 at 12:47 PM, Reinoud Koornstra
>>> <reinoudkoornstra@gmail.com> wrote:
>>> > Hi Everyone,
>>> >
>>> > Are there any plans for cavium support?
>>> > Thanks,
>>>
>>> Personally, I don't have any problems with it. I don't have their
>>> hardware to be able to test a toolchain with it. I know they have
>>> mips, mips64, and now arm(?) platforms. If you have their hardware,
>>> there is nothing stopping you from sending patches to crosstool-ng to
>>> add support.
>>
>>
>> I have been building octeon 32/64 toolchains for the last couple of
>> years. What do you mean by 'support' Reinoud?
As Mike suggested, there isn't a compiler option specific to
cavium/octeon to support this board.
However, you can just build a mips-unknown-linux-gnu or
mips64-unknown-linux-gnu, and it should work fine.
I remember building a mips64 toolchain with crosstool-ng in
2010/2011-ish for an octeon board and didn't have any issues.
Cheers,
-Bryan
>> M
>>
>>>
>>>
>>> Cheers,
>>>
>>> -Bryan
>>>
>>> > Reinoud.
>>> >
>>> > --
>>> > For unsubscribe information see http://sourceware.org/lists.html#faq
>>> >
>>>
>>> --
>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2014-12-12 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 20:47 Reinoud Koornstra
2014-12-09 22:04 ` Bryan Hundven
2014-12-11 8:43 ` M P
2014-12-11 9:13 ` Reinoud Koornstra
2014-12-12 20:38 ` Bryan Hundven [this message]
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='CAJ+oik0ofoBuP=qT8==B15aW41ve0bbV2e9ygVsB3U7zUdH3Rw@mail.gmail.com' \
--to=bryanhundven@gmail.com \
--cc=buserror@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=reinoudkoornstra@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).