From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 09/11] ARM/PPC: add a common way to access registers
Date: Thu, 04 Feb 2010 10:57:16 -0600 [thread overview]
Message-ID: <4B6AFC6C.9060809@freescale.com> (raw)
In-Reply-To: <4B6A96B3.4060803@denx.de>
Stefano Babic wrote:
> Wolfgang Denk wrote:
>
>> I like this approach better than the precious one.
>>
>> However, I had hoped that we could do without such manual configu-
>> ration like CONFIG_FSL_ESDHC_*_ENDIAN. I mean, we already know the
>> target byte order, and you know in which byte order you want to
>> access the data, or is this board dependent?
>
> It should be enough to include asm/byteorder.h. Based on __BYTE_ORDER, I
> can select the correct accessors in the driver.
How about adding additional I/O accessors that do native endian accesses instead
of specified endian?
-Scott
next prev parent reply other threads:[~2010-02-04 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 13:43 [U-Boot] [PATCH V4 09/11] ARM/PPC: add a common way to access registers Stefano Babic
2010-01-26 15:02 ` Wolfgang Denk
2010-01-29 11:28 ` Stefano Babic
2010-02-03 19:53 ` Wolfgang Denk
2010-02-04 9:43 ` Stefano Babic
2010-02-04 10:34 ` Wolfgang Denk
2010-02-04 16:57 ` Scott Wood [this message]
2010-02-05 13:05 ` Stefano Babic
2010-02-05 16:52 ` Scott Wood
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=4B6AFC6C.9060809@freescale.com \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox