From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Microblaze and Sparc boards are broken because of common timer func
Date: Mon, 18 Nov 2013 14:50:54 +0100 [thread overview]
Message-ID: <528A1B3E.2030804@monstr.eu> (raw)
In-Reply-To: <20131118132400.GA420@bill-the-cat>
On 11/18/2013 02:24 PM, Tom Rini wrote:
> On Tue, Nov 12, 2013 at 04:37:34PM +0100, Michal Simek wrote:
>> On 11/12/2013 02:46 PM, Rob Herring wrote:
>>> On 11/12/2013 06:32 AM, Michal Simek wrote:
>>>> Hi Masahiro,
>>>>
>>>> On 11/12/2013 10:04 AM, Masahiro Yamada wrote:
>>>>> Hello Michal
>>>>>
>>>>>
>>>>>> This should be fixed by this patch - at least for microblaze.
>>>>>>
>>>>>> commit 65ba7add0d609bbd035b8d42fafdaf428ac24751 Author: Rob
>>>>>> Herring <rob.herring@calxeda.com> Date: Fri Nov 8 08:40:43
>>>>>> 2013 -0600
>>>>>>
>>>>>> time: add weak annotation to timer_read_counter declaration
>>>>>>
>>>>>> A weak annotation is needed in order to prevent link errors
>>>>>> when get_ticks is overridden. This fixes sandbox build.
>>>>>>
>>>>>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>>>>>
>>>>> No. I tried both the current u-boot/master and commit
>>>>> 65ba7add0d, but Microblaze board failed with the same error
>>>>> message.
>>>>>
>>>>
>>>> Look at this log - uboot section.
>>>> http://www.monstr.eu/wiki/doku.php?id=log:2013-11-12_13_29_22
>>>>
>>>> Which toolchain do you use?
>>>
>>> It builds for me with 4.8.0 from kernel.org, but I had to disable
>>> systemace driver otherwise I get this error:
>>
>> yes. That's my behaviour too when I use this toolchain.
>> I have to ping toolchain people to find out status of stack support
>> in mainline gcc.
>
> Well, why is the assembler part failing? And what is the toolchain
> people should use here?
>
That's not question to me but to our toolchain guys what it is missing
in the mainline gcc. I have sent them an email. Will see what I get.
I do use these two toolchains[1] depends if you want to compile little
or big endian targets. Mainline u-boot, because of ll_temac driver,
must be compiled by big endian toolchains.
[1] http://www.monstr.eu/20131118-microblaze-toolchains.tar.gz
md5sum 20131118-microblaze-toolchains.tar.gz
940b8464154d3f1b58fe977156203b2a 20131118-microblaze-toolchains.tar.gz
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131118/2fe1df41/attachment.pgp>
next prev parent reply other threads:[~2013-11-18 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:12 [U-Boot] Microblaze and Sparc boards are broken because of common timer func Masahiro Yamada
2013-11-12 8:19 ` Michal Simek
2013-11-12 9:04 ` Masahiro Yamada
2013-11-12 12:32 ` Michal Simek
2013-11-12 13:46 ` Rob Herring
2013-11-12 15:37 ` Michal Simek
2013-11-18 13:24 ` Tom Rini
2013-11-18 13:50 ` Michal Simek [this message]
2013-11-14 0:37 ` Masahiro Yamada
2013-11-18 9:36 ` Michal Simek
2013-11-18 10:50 ` Masahiro Yamada
2013-11-18 10:53 ` Michal Simek
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=528A1B3E.2030804@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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