public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] zynq: Use arch_cpu_init() instead of lowlevel_init()
Date: Thu, 17 Oct 2013 14:43:25 +0200	[thread overview]
Message-ID: <20131017144325.4481a159@lilith> (raw)
In-Reply-To: <525FA009.5060203@monstr.eu>

Hi Michal,

> > Thanks for the clarification. This confirms my initial opinion that
> > NEON can be enabled in start.S on a per-board basis, as it would workin
> > all situations -- This is assuming that enabling NEON would have no
> > adverse effect on builds which do not use it, of course.
> 
> Isn't it better just to enabled it when __ARM_NEON__ is exported by gcc?
> It should mean that gcc allows to emit these instructions.

Even better. :)

> Thanks,
> Michal

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-10-17 12:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 12:52 [U-Boot] [PATCH] zynq: Use arch_cpu_init() instead of lowlevel_init() Michal Simek
2013-09-23 12:31 ` Albert ARIBAUD
2013-09-23 14:19   ` Michal Simek
2013-09-23 14:37     ` Albert ARIBAUD
2013-09-23 14:56       ` Michal Simek
2013-09-24 10:38       ` Michal Simek
2013-10-02 19:43         ` Albert ARIBAUD
2013-10-03  6:58           ` Michal Simek
2013-10-03  8:41             ` Albert ARIBAUD
2013-10-03  9:56               ` Michal Simek
2013-10-03 16:07                 ` Albert ARIBAUD
2013-10-17  6:33                   ` Albert ARIBAUD
2013-10-17  7:37                     ` Edgar E. Iglesias
2013-10-17  8:25                       ` Albert ARIBAUD
2013-10-17  8:30                         ` Michal Simek
2013-10-17 12:43                           ` Albert ARIBAUD [this message]
2013-10-17  6:49 ` Albert ARIBAUD

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=20131017144325.4481a159@lilith \
    --to=albert.u.boot@aribaud.net \
    --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