From: Chen Gang <gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Tony Breeds
<tony-B47dsA4koDqXvyopL2yb9tBPR1lH4CV8@public.gmane.org>,
linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Fengguang Wu
<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [Consult] About tool chains of metag
Date: Thu, 05 Dec 2013 09:57:21 +0800 [thread overview]
Message-ID: <529FDD81.7010000@gmail.com> (raw)
In-Reply-To: <529F5719.1000400-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Thank you very much for your details valuable information.
I will/should try my best to let it pass allmodconfig, and I guess
https://lkml.kernel.org/r/201211161520.03974.arnd-r2nGTMty4D4@public.gmane.org is valuable
to me, and I will/should reference it.
I will/should try to finish allmodconfig within one month, but excuse
me, I have to do it in my free time as a volunteer, so maybe it needs
longer (but at least, it should be finished within 2014-1-31).
Thanks.
On 12/05/2013 12:23 AM, James Hogan wrote:
> On 04/12/13 12:02, James Hogan wrote:
>> On 04/12/13 05:45, Chen Gang wrote:
>>> Could you provide any related information about metag tool chains?
>>>
>>> I plan to cross compile metag with allmodconfig, but now it seems not
>>> quite easy to find related gcc (binutils-2.23.2 support metag, but gcc
>>> main line does not).
>>
>> A buildroot tree containing a gcc-4.2.4 patch can be found here:
>>
>> git://github.com/img-meta/metag-buildroot.git metag-core
>>
>> Use meta2_defconfig
>>
>> There's a known issue with all/random config builds with this toolchain
>> which results in internal compiler errors triggered by the inline asm in
>> arch/metag/include/asm/io.h when used by certain drivers, so I need to
>> update the patch to the latest before these will go away.
>
> I've pushed a new buildroot branch which has the updated GCC 4.2.4 patch:
>
> git://github.com/img-meta/metag-buildroot.git metag-core-2013.11
> Again use meta2_defconfig.
>
> Tony: Is this something you can easily use to generate a Meta toolchain
> for https://www.kernel.org/pub/tools/crosstool/?
>
> Thanks
> James
>
>>
>> The other main issue with all/random config builds for Meta is a few
>> missing !METAG dependencies on legacy PC peripherals like SERIO_I8042,
>> which I believe you've already come across for Arc.
>>
>> Please read this thread before attempting to fix them:
>> https://lkml.kernel.org/r/201211161520.03974.arnd-r2nGTMty4D4@public.gmane.org
>>
>> I haven't got around to fixing this properly myself, but it would be a
>> worthwhile improvement if you felt inclined to do so.
>
--
Chen Gang
Open, share, and attitude like air, water and life which God blessed
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-12-05 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 5:45 [Consult] About tool chains of metag Chen Gang
[not found] ` <529EC18D.5040602-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-04 12:02 ` James Hogan
[not found] ` <529F19DA.5050805-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-04 16:23 ` James Hogan
[not found] ` <529F5719.1000400-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-05 1:57 ` Chen Gang [this message]
[not found] ` <529FDD81.7010000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-05 8:46 ` Chen Gang
[not found] ` <52A03D77.3000503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-05 9:41 ` James Hogan
[not found] ` <52A04A5F.9030001-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-05 10:20 ` Chen Gang
2013-12-08 10:25 ` Chen Gang
[not found] ` <52A4491A.2010808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-08 20:24 ` James Hogan
2013-12-09 2:21 ` 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=529FDD81.7010000@gmail.com \
--to=gang.chen.5i5j-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
--cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-B47dsA4koDqXvyopL2yb9tBPR1lH4CV8@public.gmane.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