From: Dirk Behme <dirk.behme@de.bosch.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] uboot optimize memmove
Date: Mon, 29 Jul 2013 10:28:02 +0200 [thread overview]
Message-ID: <51F62792.1020908@de.bosch.com> (raw)
In-Reply-To: <CAAfg0W7p6rvvaMqsKsC09yQnfPod08YDTbeh_MQrz6n+B4iyYA@mail.gmail.com>
On 26.07.2013 15:42, Andy Green wrote:
> On 26 July 2013 20:58, Wolfgang Denk <wd@denx.de> wrote:
...
>> you not make sure that you provide optimized implementations for such
>> functions and consequently #define __HAVE_ARCH_MEMMOVE (and
>> __HAVE_ARCH_MEMCPY) ?
>
> Yes I found these afterwards... performance is slightly better than
> memcpy() thanks to Nicolas Pitre it seems. The U-Boot config for the
> platform we have didn't know about them, it's much better with them.
>
> After I wrote this patch it was also pointed out by Will Newton at
> Linaro that we have Neon accelerated memcpy lying around with BSD
> license....
>
> https://launchpad.net/cortex-strings
>
> however for my purposes NOR boot is working good enough with the ARCH versions.
I've had a look to
https://launchpad.net/cortex-strings
and there downloaded
https://launchpad.net/cortex-strings/trunk/2013.01/+download/cortex-strings-1.0-2013.01.tar.bz2
(from the green download button on the right side).
The README mentions
src/neon contains NEON based routines for AArch32.
but the cortex-strings-1.0-2013.01.tar.bz2 seems to contain an empty
src/neon directory. Is this intended?
Best regards
Dirk
next prev parent reply other threads:[~2013-07-29 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 6:53 [U-Boot] [PATCH] uboot optimize memmove Andy Green
2013-07-26 12:58 ` Wolfgang Denk
2013-07-26 13:42 ` Andy Green
2013-07-26 19:06 ` Wolfgang Denk
2013-07-28 23:39 ` Andy Green
2013-07-29 8:03 ` Wolfgang Denk
2013-07-29 8:28 ` Dirk Behme [this message]
2013-07-29 8:44 ` Andy Green
2013-07-29 10:34 ` Will Newton
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=51F62792.1020908@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.