From: Chen Gang <gang.chen@asianux.com>
To: rkuo <rkuo@codeaurora.org>
Cc: linux-hexagon@vger.kernel.org
Subject: Re: [Suggestion] are they toolchains' issue?
Date: Wed, 06 Nov 2013 10:56:45 +0800 [thread overview]
Message-ID: <5279AFED.3000600@asianux.com> (raw)
In-Reply-To: <5274FE49.9000104@asianux.com>
On 11/02/2013 09:29 PM, Chen Gang wrote:
> On 11/02/2013 03:42 AM, rkuo wrote:
>>
>> Thanks for checking all these. There are newer Hexagon tools available
>> here:
>>
>> https://sourcery.mentor.com/GNUToolchain/release2568?cmpid=7108
>>
>> You might want to try those out. The tool prefix is hexagon-linux-, but
>> aside from that, a v4 defconfig on 3.12-rc7 compiled for me.
>>
>
> Thank you for your information.
>
I finish building the new version of gcc and binutils for kernel. And
now it can continue -- no related issues which mentioned originally
(should be fixed in this new version).
>> 'allmodconfig' does not appear to compile due to DMA related issues...
>>
>> Anyways, would you mind giving the newer tools a try?
>>
>>
>
> I will/should try. try to let our hexagon pass 'allmodconfig' within
> this month (2013-11-30).
>
I am continuing, hope we can finish within this month. :-)
Thanks.
--
Chen Gang
next prev parent reply other threads:[~2013-11-06 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 11:55 [PATCH] hexagon: include: asm: kgdb: extend DBG_MAX_REG_NUM for "cs0/1" Chen Gang
2013-11-01 12:05 ` [Suggestion] are they toolchains' issue? Chen Gang
2013-11-01 19:42 ` rkuo
2013-11-02 13:29 ` Chen Gang
2013-11-06 2:56 ` Chen Gang [this message]
2013-11-08 9:30 ` Chen Gang
2013-11-10 0:28 ` rkuo
2013-11-10 0:38 ` Chen Gang
2013-11-01 17:14 ` [PATCH] hexagon: include: asm: kgdb: extend DBG_MAX_REG_NUM for "cs0/1" Linas Vepstas
2013-11-02 13:19 ` Chen Gang
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=5279AFED.3000600@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=rkuo@codeaurora.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