diff for duplicates of <20111004175057.GU6324@atomide.com> diff --git a/a/1.txt b/N1/1.txt index d702554..6454c21 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -9,7 +9,7 @@ > >> > > > > >> > > > Furthermore... there is also a static mapping for physical address > >> > > > 0x4e000000 using virtual address 0xff100000 which is already reserved -> >> > > > for other purposes i.e. the consistent DMA area. It is not immediately +> >> > > > for other purposes i.e. the consistent DMA area. ?It is not immediately > >> > > > obvious where this comes from without being intimate with the OMAP code. > >> > > > Can this be fixed as well i.e. moved elsewhere please? > >> > > @@ -30,15 +30,15 @@ > >> > >> It looks like this comes from OMAP44XX_DMM_VIRT. > >> -> >> #define OMAP44XX_DMM_PHYS OMAP44XX_DMM_BASE -> >> /* 0x4e000000 --> 0xfd300000 */ -> >> #define OMAP44XX_DMM_VIRT (OMAP44XX_DMM_PHYS + OMAP4_L3_PER_IO_OFFSET) -> >> #define OMAP44XX_DMM_SIZE SZ_1M +> >> #define OMAP44XX_DMM_PHYS ? ? ? OMAP44XX_DMM_BASE +> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? /* 0x4e000000 --> 0xfd300000 */ +> >> #define OMAP44XX_DMM_VIRT ? ? ? (OMAP44XX_DMM_PHYS + OMAP4_L3_PER_IO_OFFSET) +> >> #define OMAP44XX_DMM_SIZE ? ? ? SZ_1M > >> > >> The comment suggesting a mapping correspondance is obviously wrong. We have: > >> -> >> #define OMAP44XX_DMM_BASE 0x4e000000 -> >> #define OMAP4_L3_PER_IO_OFFSET 0xb1100000 +> >> #define OMAP44XX_DMM_BASE ? ? ? 0x4e000000 +> >> #define OMAP4_L3_PER_IO_OFFSET ?0xb1100000 > >> > >> Hence 0x4e000000 + 0xb1100000 = 0xff100000. > > @@ -46,12 +46,8 @@ > > Santosh, can youp please check it? > > > This is already fixed Tony. You have pulled that patch. -> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg55258.html +> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg55258.html OK thanks. Yup, looks like it's queued up in l3 branch. Tony --- -To unsubscribe from this list: send the line "unsubscribe linux-omap" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 66b6052..78e4aae 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,14 +4,10 @@ "ref\0alpine.LFD.2.02.1110031827440.9106@xanadu.home\0" "ref\020111003225908.GL6324@atomide.com\0" "ref\0CAMQu2gxgRZzb6hh5pOVBgaPUZEizEqBr_e358MBuD_xHJOvX3Q@mail.gmail.com\0" - "From\0Tony Lindgren <tony@atomide.com>\0" - "Subject\0Re: Please help with the OMAP static mapping mess\0" + "From\0tony@atomide.com (Tony Lindgren)\0" + "Subject\0Please help with the OMAP static mapping mess\0" "Date\0Tue, 4 Oct 2011 10:50:57 -0700\0" - "To\0Shilimkar" - " Santosh <santosh.shilimkar@ti.com>\0" - "Cc\0linux-omap@vger.kernel.org" - linux-arm-kernel@lists.infradead.org - " Nicolas Pitre <nico@fluxnic.net>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "* Shilimkar, Santosh <santosh.shilimkar@ti.com> [111003 22:45]:\n" @@ -25,7 +21,7 @@ "> >> > > >\n" "> >> > > > Furthermore... there is also a static mapping for physical address\n" "> >> > > > 0x4e000000 using virtual address 0xff100000 which is already reserved\n" - "> >> > > > for other purposes i.e. the consistent DMA area. \302\240It is not immediately\n" + "> >> > > > for other purposes i.e. the consistent DMA area. ?It is not immediately\n" "> >> > > > obvious where this comes from without being intimate with the OMAP code.\n" "> >> > > > Can this be fixed as well i.e. moved elsewhere please?\n" "> >> > >\n" @@ -46,15 +42,15 @@ "> >>\n" "> >> It looks like this comes from OMAP44XX_DMM_VIRT.\n" "> >>\n" - "> >> #define OMAP44XX_DMM_PHYS \302\240 \302\240 \302\240 OMAP44XX_DMM_BASE\n" - "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 /* 0x4e000000 --> 0xfd300000 */\n" - "> >> #define OMAP44XX_DMM_VIRT \302\240 \302\240 \302\240 (OMAP44XX_DMM_PHYS + OMAP4_L3_PER_IO_OFFSET)\n" - "> >> #define OMAP44XX_DMM_SIZE \302\240 \302\240 \302\240 SZ_1M\n" + "> >> #define OMAP44XX_DMM_PHYS ? ? ? OMAP44XX_DMM_BASE\n" + "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? /* 0x4e000000 --> 0xfd300000 */\n" + "> >> #define OMAP44XX_DMM_VIRT ? ? ? (OMAP44XX_DMM_PHYS + OMAP4_L3_PER_IO_OFFSET)\n" + "> >> #define OMAP44XX_DMM_SIZE ? ? ? SZ_1M\n" "> >>\n" "> >> The comment suggesting a mapping correspondance is obviously wrong. We have:\n" "> >>\n" - "> >> #define OMAP44XX_DMM_BASE \302\240 \302\240 \302\240 0x4e000000\n" - "> >> #define OMAP4_L3_PER_IO_OFFSET \302\2400xb1100000\n" + "> >> #define OMAP44XX_DMM_BASE ? ? ? 0x4e000000\n" + "> >> #define OMAP4_L3_PER_IO_OFFSET ?0xb1100000\n" "> >>\n" "> >> Hence 0x4e000000 + 0xb1100000 = 0xff100000.\n" "> >\n" @@ -62,14 +58,10 @@ "> > Santosh, can youp please check it?\n" "> >\n" "> This is already fixed Tony. You have pulled that patch.\n" - "> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg55258.html\n" + "> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg55258.html\n" "\n" "OK thanks. Yup, looks like it's queued up in l3 branch.\n" "\n" - "Tony\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-omap\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Tony -3e378850a359bf3f63007187b07cd7d189e48c19ad7c5df87d2f201443a3fa29 +5087521d6878d50654948ac52e63e7eacf1217ff0cbdaad1c9d373bd97ff5696
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.