public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC/PATCH] fix initdram / use of phys_addr_t
Date: Wed, 12 Mar 2008 12:02:40 -0500	[thread overview]
Message-ID: <47D80CB0.30100@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803121037440.13065@blarg.am.freescale.net>

Kumar Gala wrote:
> Wolfgang,
> 
> Before I went and looked at every board that uses initdram I wanted to get
> some feedback of such a patch (for a wide majority of boards) would be
> acceptable.
> 
> The idea is that initdram() should really have returned a 'unsigned long'.
> However if we are going to change everyone that has initdram I figure we
> should make it return a phys_addr_t.
> 
> I believe you've had some discussions with Jon on the subject and I wanted
> to know if using 'phys_addr_t' here would be acceptable (before I looked
> at trying to fix up ~200 boards).
> 
> The patch gives an example of what I'm looking at changing.
> 
> - k

Just FYI, I am in full support of this proposed change to
use phys_addr_t.


> index cd8aad0..229d15a 100644
> --- a/include/common.h
> +++ b/include/common.h
> @@ -107,6 +107,8 @@ typedef volatile unsigned char	vu_char;
>  #include <asm/blackfin.h>
>  #endif
> 
> +#include <asm/io.h>
> +

I don't think asm/io.h is the right place for phys_addr_t.
However, adding it to asm/types.h might me.  That is where
Becky and I have been headed...

jdl

  reply	other threads:[~2008-03-12 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 15:38 [U-Boot-Users] [RFC/PATCH] fix initdram / use of phys_addr_t Kumar Gala
2008-03-12 17:02 ` Jon Loeliger [this message]
2008-03-12 18:40 ` Wolfgang Denk
2008-03-12 19:09   ` Kumar Gala
2008-03-12 19:23     ` Jerry Van Baren
2008-03-12 20:52       ` Wolfgang Denk
2008-03-12 20:50     ` Wolfgang Denk
2008-03-12 22:25 ` Jean-Christophe PLAGNIOL-VILLARD
2008-03-12 23:12   ` Kumar Gala
2008-03-12 23:18     ` Jon Loeliger
2008-03-13  0:06     ` Wolfgang Denk

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=47D80CB0.30100@freescale.com \
    --to=jdl@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