From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: dcache: Replace ext_csd buffer with cache aligned one
Date: Fri, 12 Aug 2011 11:50:13 +0200 [thread overview]
Message-ID: <4E44F755.3020907@aribaud.net> (raw)
In-Reply-To: <20110812113506.5b734746@lmajewski.digital.local>
Hi Lukasz,
On 12/08/2011 11:35, Lukasz Majewski wrote:
> Hi Albert,
>
> On Fri, 12 Aug 2011 11:07:57 +0200
> Albert ARIBAUD<albert.u.boot@aribaud.net> wrote:
>
>> I know it is in GNU LIBC; I also know it is not (yet...) in U-Boot's
>> own C library. What about the most common toolchains used on U-Boot?
>
> The memalign is already defined in the u-boot tree (common/dlmalloc.c).
Apologies: seems like I missed it.
> The dlmalloc.o is also built during compilation and it is linked to the
> final u-boot binary.
>
> I'm using the CodeSourgery's ARM toolchain (gcc version 4.4.1 (Sourcery
> G++ Lite 2009q3-68)).
> I can test it with (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72)) as
> well.
>
> Moreover I can try to install OSELAS.Toolchain (PTXdist ones) and test
> this as well with those toolchains. There are several one available for
> armv5/armv6/armv7.
>
> Initially I was planning to use calloc/malloc from ./common/dlmalloc.c
> but it is clearly stated, that it is using 8 bytes alignment (which is
> hardwired in this implementation).
>
> I will keep you informed about the tests results.
Thanks a lot! If no toolchain gives issues, then I guess the use of
memalign() for dynamic buffers can be considered the way to go.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-08-12 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 8:25 [U-Boot] [PATCH] mmc: dcache: Replace ext_csd buffer with cache aligned one Lukasz Majewski
2011-08-12 9:07 ` Albert ARIBAUD
2011-08-12 9:35 ` Lukasz Majewski
2011-08-12 9:50 ` Albert ARIBAUD [this message]
2011-08-17 2:43 ` Andy Fleming
2011-08-17 9:33 ` [U-Boot] [PATCH v2] " Lukasz Majewski
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=4E44F755.3020907@aribaud.net \
--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 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.