public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 6/6] cfi_flash: Use map_physmem() and unmap_physmem()
Date: Wed, 12 Dec 2007 11:24:14 +0100	[thread overview]
Message-ID: <200712121124.15239.sr@denx.de> (raw)
In-Reply-To: <20071212103632.5e0a0f97@dhcp-252-066.norway.atmel.com>

On Wednesday 12 December 2007, Haavard Skinnemoen wrote:
> > When starting something like map_physmem(), we should consider the
> > following things:
> >
> > - Some platforms have >32bit physical address space, like PPC440 with
> > 36bits. So the type of phys_addr should not be fixed to u32. We need a
> > new typedef here. And/or perhaps something like the resource stuff from
> > Linux.
>
> Yeah, we probably need a typedef. How about phys_addr_t or something?

ACK.

> I can cook up a patch adding phys_addr_t typedef'd as unsigned long on
> all architectures. If someone wants something different, please let me
> know.

Yes, start with "unsigned long" and the platform maintainer can fix this later 
if needed. This way we can get this started right now.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-12-12 10:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 15:28 [U-Boot-Users] [PATCH 0/6] cfi_flash cleanups Haavard Skinnemoen
2007-12-11 15:28 ` [U-Boot-Users] [PATCH 1/6] cfi_flash: Break long lines Haavard Skinnemoen
2007-12-11 15:28   ` [U-Boot-Users] [PATCH 2/6] cfi_flash: Make some needlessly global functions static Haavard Skinnemoen
     [not found]     ` <1197386900-14570-4-git-send-email-hskinnemoen@atmel.com>
2007-12-11 15:28       ` [U-Boot-Users] [PATCH 4/6] cfi_flash: Introduce read and write accessors Haavard Skinnemoen
2007-12-11 15:28         ` [U-Boot-Users] [PATCH 5/6] Introduce map_physmem() and unmap_physmem() Haavard Skinnemoen
2007-12-11 15:28           ` [U-Boot-Users] [PATCH 6/6] cfi_flash: Use " Haavard Skinnemoen
2007-12-11 15:36             ` Kumar Gala
2007-12-11 15:43               ` Haavard Skinnemoen
2007-12-11 18:49                 ` Stefan Roese
2007-12-12  9:36                   ` Haavard Skinnemoen
2007-12-12 10:24                     ` Stefan Roese [this message]
2007-12-11 22:10             ` Wolfgang Denk
2007-12-11 22:55               ` Andrew Dyer
2007-12-12  6:09                 ` Stefan Roese
2007-12-12  9:23               ` Haavard Skinnemoen
2007-12-11 15:35         ` [U-Boot-Users] [PATCH 4/6] cfi_flash: Introduce read and write accessors Kumar Gala
2007-12-11 15:46           ` Haavard Skinnemoen
2007-12-11 16:25             ` Wolfgang Denk
2007-12-11 17:13               ` Haavard Skinnemoen
2007-12-11 18:59                 ` Stefan Roese
2007-12-11 22:05                 ` Wolfgang Denk
2007-12-12  9:31                   ` Haavard Skinnemoen
2007-12-13 11:04   ` [U-Boot-Users] [PATCH 1/6] cfi_flash: Break long lines Stefan Roese
2007-12-11 19:04 ` [U-Boot-Users] [PATCH 0/6] cfi_flash cleanups Stefan Roese
2007-12-12 10:01   ` Haavard Skinnemoen

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=200712121124.15239.sr@denx.de \
    --to=sr@denx.de \
    --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