All of lore.kernel.org
 help / color / mirror / Atom feed
From: "pascal@pabr.org" <pascal@pabr.org>
To: linux-mips@linux-mips.org
Subject: [RFC] Support 36-bit iomem on 32-bit Au1x00
Date: Sun, 03 Jan 2010 13:39:12 +0100	[thread overview]
Message-ID: <hhq35v$m1q$1@ger.gmane.org> (raw)

Hi,

I believe these changes are needed on Alchemy SoCs in order to
use iomem above 4G with the usual platform_device machinery:

- Set CONFIG_ARCH_PHYS_ADDR_T_64BIT to make resource_size_t 64-bit.
- Increase IOMEM_RESOURCE_END so that platforms can register resources.


--- linux-2.6.33-rc2/arch/mips/Kconfig.orig     2009-12-30 18:06:02.000000000 +0100
+++ linux-2.6.33-rc2/arch/mips/Kconfig  2009-12-30 22:05:38.000000000 +0100
@@ -1725,6 +1725,9 @@
 config 64BIT_PHYS_ADDR
        bool

+config ARCH_PHYS_ADDR_T_64BIT
+       def_bool 64BIT_PHYS_ADDR
+
 config CPU_HAS_SMARTMIPS
        depends on SYS_SUPPORTS_SMARTMIPS
        bool "Support for the SmartMIPS ASE"
--- linux-2.6.33-rc2/arch/mips/include/asm/mach-au1x00/au1000.h.orig    2009-12-30 19:45:35.000000000 +0100
+++ linux-2.6.33-rc2/arch/mips/include/asm/mach-au1x00/au1000.h 2010-01-03 13:28:50.000000000 +0100
@@ -1728,7 +1728,7 @@
 #define IOPORT_RESOURCE_START  0x10000000
 #define IOPORT_RESOURCE_END    0xffffffff
 #define IOMEM_RESOURCE_START   0x10000000
-#define IOMEM_RESOURCE_END     0xffffffff
+#define IOMEM_RESOURCE_END     0xfffffffffLL

 #define PCI_IO_START   0
 #define PCI_IO_END     0

             reply	other threads:[~2010-01-03 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 12:39 pascal [this message]
2010-01-26 20:46 ` [RFC] Support 36-bit iomem on 32-bit Au1x00 Manuel Lauss
2010-01-26 21:19   ` pascal
2010-01-28 13:18     ` Ralf Baechle
2010-01-28 13:22       ` Manuel Lauss
2010-01-28 13:53         ` Ralf Baechle

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='hhq35v$m1q$1@ger.gmane.org' \
    --to=pascal@pabr.org \
    --cc=linux-mips@linux-mips.org \
    /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.