From: FengHua <fenghua@phytium.com.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Add 64-bit data support for memory commands
Date: Thu, 13 Feb 2014 10:41:07 +0800 (GMT+08:00) [thread overview]
Message-ID: <abf055.dad.144291e7cc7.Coremail.fenghua@phytium.com.cn> (raw)
In-Reply-To: <20140212221101.A5F0338060E@gemini.denx.de>
> -----Original Messages-----
> From: "Wolfgang Denk" <wd@denx.de>
> Sent Time: 2014-02-13 06:11:01 (Thursday)
> To: "York Sun" <yorksun@freescale.com>
> Cc: scottwood at freescale.com, u-boot at lists.denx.de
> Subject: Re: [U-Boot] [RFC] Add 64-bit data support for memory commands
>
> Dear York Sun,
>
> In message <1392240023-25205-1-git-send-email-yorksun@freescale.com> you wrote:
> > For aarch64, unsigned long is 64-bit data. Memory commands should be fixed
> > with u32 for 32-bit address access. A double word data size is added to
> > support 64-bit data.
> >
> > Signed-off-by: York Sun <yorksun@freescale.com>
>
> Can you please make all this code conditional for 64 bit architectures
> only, so that 32 bit systems do not suffer from the increased code
> size?
>
> Thanks.
>
> Best regards,
>
> Wolfgang Denk
How about use some macro from compiler of sizeof(long)?
Maybe this could avoid conditional switch, and cmd_mem work with 32 and 64 bit platform.
Best Wishes
next prev parent reply other threads:[~2014-02-13 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 21:20 [U-Boot] [RFC] Add 64-bit data support for memory commands York Sun
2014-02-12 22:11 ` Wolfgang Denk
2014-02-12 22:23 ` York Sun
2014-02-12 22:42 ` York Sun
2014-02-13 2:29 ` Albert ARIBAUD
2014-02-13 5:27 ` Wolfgang Denk
2014-02-13 2:41 ` FengHua [this message]
2014-02-13 2:56 ` Albert ARIBAUD
2014-02-13 2:57 ` York Sun
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=abf055.dad.144291e7cc7.Coremail.fenghua@phytium.com.cn \
--to=fenghua@phytium.com.cn \
--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.