Re: [PATCH] fix omap3 sram virtual addres overlap vmalloc space after increasing vmalloc size

2009-07-21 Thread Janboe Ye
Thanks, Paul

Tony

Is there some issue about this patch?

Thanks

Janboe Ye

On Fri, 2009-07-17 at 16:04 -0600, Paul Walmsley wrote:
 On Thu, 16 Jul 2009, Janboe Ye wrote:
 
  resend for mini coding style fixing
  
  commit e85c205ac1427f2405021a36f083280ff0d0a35e increase vmalloc size.
  vmalloc space will overlap with OMAP3 sram virtual address.
 
 Makes sense to me.  I'm not sure how we missed this in the original patch.
 
 Reviewed-by: Paul Walmsley p...@pwsan.com
 
 - Paul
 
  
  Signed-off-by: Li Hong Mei hong-mei...@motorola.com
  Signed-off-by: Janboe Ye yuan-bo...@motorola.com
  ---
   arch/arm/plat-omap/sram.c |4 ++--
   1 files changed, 2 insertions(+), 2 deletions(-)
  
  diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
  index a2e60e7..755ccaa 100644
  --- a/arch/arm/plat-omap/sram.c
  +++ b/arch/arm/plat-omap/sram.c
  @@ -41,9 +41,9 @@
   #define OMAP2_SRAM_VA  0xe300
   #define OMAP2_SRAM_PUB_VA  (OMAP2_SRAM_VA + 0x800)
   #define OMAP3_SRAM_PA   0x4020
  -#define OMAP3_SRAM_VA   0xd700
  +#define OMAP3_SRAM_VA   0xe300
   #define OMAP3_SRAM_PUB_PA   0x40208000
  -#define OMAP3_SRAM_PUB_VA   0xd7008000
  +#define OMAP3_SRAM_PUB_VA   (OMAP3_SRAM_VA + 0x8000)
  
   #if defined(CONFIG_ARCH_OMAP24XX) || defined(CONFIG_ARCH_OMAP34XX)
   #define SRAM_BOOTLOADER_SZ 0x00
  
 
 
 - Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH] fix omap3 sram virtual addres overlap vmalloc space after increasing vmalloc size

2009-07-16 Thread Janboe Ye
commit e85c205ac1427f2405021a36f083280ff0d0a35e increase vmalloc size.
vmalloc space will overlap with OMAP3 sram virtual address.

Signed-off-by: Li Hong Mei hong-mei...@motorola.com
Signed-off-by: Janboe Ye yuan-bo...@motorola.com
---
 arch/arm/plat-omap/sram.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
index a2e60e7..92e609b 100644
--- a/arch/arm/plat-omap/sram.c
+++ b/arch/arm/plat-omap/sram.c
@@ -41,9 +41,9 @@
 #define OMAP2_SRAM_VA  0xe300
 #define OMAP2_SRAM_PUB_VA  (OMAP2_SRAM_VA + 0x800)
 #define OMAP3_SRAM_PA   0x4020
-#define OMAP3_SRAM_VA   0xd700
+#define OMAP3_SRAM_VA   0xe300
 #define OMAP3_SRAM_PUB_PA   0x40208000
-#define OMAP3_SRAM_PUB_VA   0xd7008000
+#define OMAP3_SRAM_PUB_VA   (OMAP3_SRAM_VA + 0X8000)

 #if defined(CONFIG_ARCH_OMAP24XX) || defined(CONFIG_ARCH_OMAP34XX)
 #define SRAM_BOOTLOADER_SZ 0x00

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH] fix omap3 sram virtual addres overlap vmalloc space after increasing vmalloc size

2009-07-16 Thread Janboe Ye
resend for mini coding style fixing

commit e85c205ac1427f2405021a36f083280ff0d0a35e increase vmalloc size.
vmalloc space will overlap with OMAP3 sram virtual address.

Signed-off-by: Li Hong Mei hong-mei...@motorola.com
Signed-off-by: Janboe Ye yuan-bo...@motorola.com
---
 arch/arm/plat-omap/sram.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
index a2e60e7..755ccaa 100644
--- a/arch/arm/plat-omap/sram.c
+++ b/arch/arm/plat-omap/sram.c
@@ -41,9 +41,9 @@
 #define OMAP2_SRAM_VA  0xe300
 #define OMAP2_SRAM_PUB_VA  (OMAP2_SRAM_VA + 0x800)
 #define OMAP3_SRAM_PA   0x4020
-#define OMAP3_SRAM_VA   0xd700
+#define OMAP3_SRAM_VA   0xe300
 #define OMAP3_SRAM_PUB_PA   0x40208000
-#define OMAP3_SRAM_PUB_VA   0xd7008000
+#define OMAP3_SRAM_PUB_VA   (OMAP3_SRAM_VA + 0x8000)

 #if defined(CONFIG_ARCH_OMAP24XX) || defined(CONFIG_ARCH_OMAP34XX)
 #define SRAM_BOOTLOADER_SZ 0x00

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html