public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Zynq SoC changes
Date: Fri, 23 Jan 2015 15:33:32 +0100	[thread overview]
Message-ID: <54C25BBC.7080309@monstr.eu> (raw)
In-Reply-To: <20150123141204.GJ10826@bill-the-cat>

On 01/23/2015 03:12 PM, Tom Rini wrote:
> On Fri, Jan 23, 2015 at 02:39:44PM +0100, Michal Simek wrote:
>> On 01/23/2015 12:59 PM, Tom Rini wrote:
>>> On Fri, Jan 23, 2015 at 10:02:04AM +0100, Michal Simek wrote:
>>>> On 01/23/2015 02:05 AM, Tom Rini wrote:
>>>>> On Wed, Jan 21, 2015 at 10:38:47AM +0100, Michal Simek wrote:
>>>>>
>>>>>> Hi Tom,
>>>>>>
>>>>>> please pull these patches to your tree. I have added there 2 patches
>>>>>> for serial. Zynq is only one platform which is using this driver.
>>>>>>
>>>>>> Thanks,
>>>>>> Michal
>>>>>>
>>>>>> The following changes since commit 92fa7f53f1f3f03296f8ffb14bdf1baefab83368:
>>>>>>
>>>>>>   Prepare v2015.01 (2015-01-12 09:39:08 -0500)
>>>>>>
>>>>>> are available in the git repository at:
>>>>>>
>>>>>>   git://www.denx.de/git/u-boot-microblaze.git zynq
>>>>>>
>>>>>> for you to fetch changes up to 025216f78e0dacd491908d0d76a3642630cd84dc:
>>>>>>
>>>>>>   serial: Extend structure comments with register offset (2015-01-21 10:36:36 +0100)
>>>>>>
>>>>>
>>>>> I can't find a toolchain that doesn't give me something like:
>>>>>  arm: +   zynq_zc70x
>>>>> +(zynq_zc70x) arch/arm/cpu/armv7/zynq/lowlevel_init.S: Assembler messages:
>>>>> +(zynq_zc70x) arch/arm/cpu/armv7/zynq/lowlevel_init.S:19: Error: selected processor doe
>>>>> s not support ARM mode `fmrx r1,FPEXC'
>>>>> +(zynq_zc70x) arch/arm/cpu/armv7/zynq/lowlevel_init.S:21: Error: selected processor does not support ARM mode `fmxr FPEXC,r1'
>>>>> +(zynq_zc70x) make[3]: *** [arch/arm/cpu/armv7/zynq/lowlevel_init.o] Error 1
>>>>> +(zynq_zc70x) make[2]: *** [arch/arm/cpu/armv7/zynq] Error 2
>>>>> +(zynq_zc70x) make[1]: *** [arch/arm/cpu/armv7] Error 2
>>>>> +(zynq_zc70x) make: *** [sub-make] Error 2
>>>>>
>>>>
>>>> ok. I see. We have neon instructions enabled by default in xilinx toolchain.
>>>> I have sent the patch which create and add
>>>> PLATFORM_RELFLAGS += -mfpu=neon
>>>> to config.mk.
>>>>
>>>> This should solve the problem with compilation.
>>>> No problem to add this patch as the first in this serial not to break bisectability
>>>> of the tree.
>>>
>>> And we have a _really_ good reason for using FPU instructions, yes?
>>
>> The description for doing that is in the patch but to be honest the biggest problem
>> is that xilinx toolchain has FPU instructions enabled by default. Based on that fpu instructions
>> can be used. For standard xilinx flow FSBL/u-boot - fsbl does that setting.
>> For debug flow TCL + u-boot we are reaching this issue.
>>
>> Maybe the second option can be to disable FPU instructions for u-boot compilation
>> but then the problem is moved to next software which is designed to have FPU instructions
>> enabled.
>> That's why I think it is just better to enable it in u-boot.
>>
>> Siva: Feel free to correct me if my understanding is not correct.
> 
> And for the record and clarity, we're still not actually using the FPU
> in U-Boot nor intend to, just enabling normal workflows on these
> platforms, right?

Yes, correct.

M

-- 
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: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150123/f984dfe3/attachment.pgp>

  reply	other threads:[~2015-01-23 14:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  9:38 [U-Boot] [GIT PULL] Zynq SoC changes Michal Simek
2015-01-23  1:05 ` Tom Rini
2015-01-23  9:02   ` Michal Simek
2015-01-23 11:59     ` Tom Rini
2015-01-23 13:39       ` Michal Simek
2015-01-23 14:12         ` Tom Rini
2015-01-23 14:33           ` Michal Simek [this message]
2015-01-23 15:19             ` Tom Rini
2015-01-26  8:09               ` [U-Boot] [GIT PULL] Zynq SoC changes v2 Michal Simek
2015-01-27 11:51                 ` Tom Rini
2015-01-26 15:42     ` [U-Boot] [GIT PULL] Zynq SoC changes Bill Pringlemeir

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=54C25BBC.7080309@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