All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1461851171.3673.30.camel@synopsys.com>

diff --git a/a/1.txt b/N1/1.txt
index 43b8cda..c6972ad 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 Hi Vineet,
 
-On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:
+On Thu, 2016-04-28 at 09:56 +0530, Vineet Gupta wrote:
 
 [snip]
 
@@ -10,9 +10,9 @@ On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:
 > > --- a/arch/arc/boot/dts/axc001.dtsi
 > > +++ b/arch/arc/boot/dts/axc001.dtsi
 > > @@ -95,6 +95,24 @@
-> > ?		#size-cells = <1>;
-> > ?		ranges = <0x00000000 0x80000000 0x40000000>;
-> > ?		device_type = "memory";
+> >  		#size-cells = <1>;
+> >  		ranges = <0x00000000 0x80000000 0x40000000>;
+> >  		device_type = "memory";
 > > -		reg = <0x80000000 0x20000000>;	/* 512MiB */
 > > +		reg = <0x80000000 0x1f000000>;	/* 512 - 16 MiB */
 > Is 16MB fixed size or is this a function of display resolution / density etc.
@@ -24,7 +24,7 @@ So as of now the corner case would be 1920x1080, 16 bits per pixel
 which gives ~4Mb. Now if we add support of triple-buffering we'll
 need ~12Mb so I booked a little bit more - 16Mb.
 
-But now I recalled that we also support?r8g8b8 mode and in this case
+But now I recalled that we also support r8g8b8 mode and in this case
 3 bytes are used for color encoding, which effectively gives ~6Mb for
 1 FullHD frame. And for tripple-buffering we'll need > 18Mb, so probably
 we'll need to go for 24 or even 32 Mb.
@@ -37,9 +37,9 @@ we'll need to go for 24 or even 32 Mb.
 > > +		#size-cells = <1>;
 > > +		ranges;
 > > +		/*
-> > +		?* Move frame buffer out of IOC aperture (0x8z-0xAz).
-> > +		?*/
-> > +		frame_buffer: frame_buffer at bf000000 {
+> > +		 * Move frame buffer out of IOC aperture (0x8z-0xAz).
+> > +		 */
+> > +		frame_buffer: frame_buffer@bf000000 {
 > > +			compatible = "shared-dma-pool";
 > > +			reg = <0xbf000000 0x1000000>;
 > Can this be made a bit more future safe. AXS103 has 1 GB of DDR while kernel
@@ -53,4 +53,7 @@ Makes sense. Will move it to the very end of 1Gb.
 
 What do you mean by that?
 
--Alexey
+-Alexey--
+To unsubscribe from this list: send the line "unsubscribe devicetree" in
+the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index e8eab62..66afe1e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,15 +1,20 @@
  "ref\01461767701-12208-1-git-send-email-abrodkin@synopsys.com\0"
  "ref\01461767701-12208-3-git-send-email-abrodkin@synopsys.com\0"
  "ref\0572190F3.3020709@synopsys.com\0"
- "From\0Alexey.Brodkin@synopsys.com (Alexey Brodkin)\0"
- "Subject\0[PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer\0"
+ "ref\0572190F3.3020709-HKixBCOQz3hWk0Htik3J/w@public.gmane.org\0"
+ "From\0Alexey Brodkin <Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>\0"
+ "Subject\0Re: [PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer\0"
  "Date\0Thu, 28 Apr 2016 13:46:22 +0000\0"
- "To\0linux-snps-arc@lists.infradead.org\0"
+ "To\0Vineet Gupta <Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>\0"
+ "Cc\0dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org <dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>"
+  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
+  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
+ " linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "Hi Vineet,\n"
  "\n"
- "On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:\n"
+ "On Thu, 2016-04-28 at 09:56 +0530, Vineet Gupta wrote:\n"
  "\n"
  "[snip]\n"
  "\n"
@@ -19,9 +24,9 @@
  "> > --- a/arch/arc/boot/dts/axc001.dtsi\n"
  "> > +++ b/arch/arc/boot/dts/axc001.dtsi\n"
  "> > @@ -95,6 +95,24 @@\n"
- "> > ?\t\t#size-cells = <1>;\n"
- "> > ?\t\tranges = <0x00000000 0x80000000 0x40000000>;\n"
- "> > ?\t\tdevice_type = \"memory\";\n"
+ "> > \302\240\t\t#size-cells = <1>;\n"
+ "> > \302\240\t\tranges = <0x00000000 0x80000000 0x40000000>;\n"
+ "> > \302\240\t\tdevice_type = \"memory\";\n"
  "> > -\t\treg = <0x80000000 0x20000000>;\t/* 512MiB */\n"
  "> > +\t\treg = <0x80000000 0x1f000000>;\t/* 512 - 16 MiB */\n"
  "> Is 16MB fixed size or is this a function of display resolution / density etc.\n"
@@ -33,7 +38,7 @@
  "which gives ~4Mb. Now if we add support of triple-buffering we'll\n"
  "need ~12Mb so I booked a little bit more - 16Mb.\n"
  "\n"
- "But now I recalled that we also support?r8g8b8 mode and in this case\n"
+ "But now I recalled that we also support\302\240r8g8b8 mode and in this case\n"
  "3 bytes are used for color encoding, which effectively gives ~6Mb for\n"
  "1 FullHD frame. And for tripple-buffering we'll need > 18Mb, so probably\n"
  "we'll need to go for 24 or even 32 Mb.\n"
@@ -46,9 +51,9 @@
  "> > +\t\t#size-cells = <1>;\n"
  "> > +\t\tranges;\n"
  "> > +\t\t/*\n"
- "> > +\t\t?* Move frame buffer out of IOC aperture (0x8z-0xAz).\n"
- "> > +\t\t?*/\n"
- "> > +\t\tframe_buffer: frame_buffer at bf000000 {\n"
+ "> > +\t\t\302\240* Move frame buffer out of IOC aperture (0x8z-0xAz).\n"
+ "> > +\t\t\302\240*/\n"
+ "> > +\t\tframe_buffer: frame_buffer@bf000000 {\n"
  "> > +\t\t\tcompatible = \"shared-dma-pool\";\n"
  "> > +\t\t\treg = <0xbf000000 0x1000000>;\n"
  "> Can this be made a bit more future safe. AXS103 has 1 GB of DDR while kernel\n"
@@ -62,6 +67,9 @@
  "\n"
  "What do you mean by that?\n"
  "\n"
- -Alexey
+ "-Alexey--\n"
+ "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n"
+ "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n"
+ More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
-5d48dc9141f94d82bd33e2488a823618d5909088c631413b84d77d29ec10483a
+e261d80786917304136cd4ebf69c0335c1ad6e2b20bc62c55a92fa3a653295b8

diff --git a/a/1.txt b/N2/1.txt
index 43b8cda..1ebe40e 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,6 +1,6 @@
 Hi Vineet,
 
-On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:
+On Thu, 2016-04-28 at 09:56 +0530, Vineet Gupta wrote:
 
 [snip]
 
@@ -10,9 +10,9 @@ On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:
 > > --- a/arch/arc/boot/dts/axc001.dtsi
 > > +++ b/arch/arc/boot/dts/axc001.dtsi
 > > @@ -95,6 +95,24 @@
-> > ?		#size-cells = <1>;
-> > ?		ranges = <0x00000000 0x80000000 0x40000000>;
-> > ?		device_type = "memory";
+> >  		#size-cells = <1>;
+> >  		ranges = <0x00000000 0x80000000 0x40000000>;
+> >  		device_type = "memory";
 > > -		reg = <0x80000000 0x20000000>;	/* 512MiB */
 > > +		reg = <0x80000000 0x1f000000>;	/* 512 - 16 MiB */
 > Is 16MB fixed size or is this a function of display resolution / density etc.
@@ -24,7 +24,7 @@ So as of now the corner case would be 1920x1080, 16 bits per pixel
 which gives ~4Mb. Now if we add support of triple-buffering we'll
 need ~12Mb so I booked a little bit more - 16Mb.
 
-But now I recalled that we also support?r8g8b8 mode and in this case
+But now I recalled that we also support r8g8b8 mode and in this case
 3 bytes are used for color encoding, which effectively gives ~6Mb for
 1 FullHD frame. And for tripple-buffering we'll need > 18Mb, so probably
 we'll need to go for 24 or even 32 Mb.
@@ -37,9 +37,9 @@ we'll need to go for 24 or even 32 Mb.
 > > +		#size-cells = <1>;
 > > +		ranges;
 > > +		/*
-> > +		?* Move frame buffer out of IOC aperture (0x8z-0xAz).
-> > +		?*/
-> > +		frame_buffer: frame_buffer at bf000000 {
+> > +		 * Move frame buffer out of IOC aperture (0x8z-0xAz).
+> > +		 */
+> > +		frame_buffer: frame_buffer@bf000000 {
 > > +			compatible = "shared-dma-pool";
 > > +			reg = <0xbf000000 0x1000000>;
 > Can this be made a bit more future safe. AXS103 has 1 GB of DDR while kernel
diff --git a/a/content_digest b/N2/content_digest
index e8eab62..0acf4fe 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,15 +1,19 @@
  "ref\01461767701-12208-1-git-send-email-abrodkin@synopsys.com\0"
  "ref\01461767701-12208-3-git-send-email-abrodkin@synopsys.com\0"
  "ref\0572190F3.3020709@synopsys.com\0"
- "From\0Alexey.Brodkin@synopsys.com (Alexey Brodkin)\0"
- "Subject\0[PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer\0"
+ "From\0Alexey Brodkin <Alexey.Brodkin@synopsys.com>\0"
+ "Subject\0Re: [PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer\0"
  "Date\0Thu, 28 Apr 2016 13:46:22 +0000\0"
- "To\0linux-snps-arc@lists.infradead.org\0"
+ "To\0Vineet Gupta <Vineet.Gupta1@synopsys.com>\0"
+ "Cc\0dri-devel@lists.freedesktop.org <dri-devel@lists.freedesktop.org>"
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  devicetree@vger.kernel.org <devicetree@vger.kernel.org>
+ " linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "Hi Vineet,\n"
  "\n"
- "On Thu, 2016-04-28@09:56 +0530, Vineet Gupta wrote:\n"
+ "On Thu, 2016-04-28 at 09:56 +0530, Vineet Gupta wrote:\n"
  "\n"
  "[snip]\n"
  "\n"
@@ -19,9 +23,9 @@
  "> > --- a/arch/arc/boot/dts/axc001.dtsi\n"
  "> > +++ b/arch/arc/boot/dts/axc001.dtsi\n"
  "> > @@ -95,6 +95,24 @@\n"
- "> > ?\t\t#size-cells = <1>;\n"
- "> > ?\t\tranges = <0x00000000 0x80000000 0x40000000>;\n"
- "> > ?\t\tdevice_type = \"memory\";\n"
+ "> > \302\240\t\t#size-cells = <1>;\n"
+ "> > \302\240\t\tranges = <0x00000000 0x80000000 0x40000000>;\n"
+ "> > \302\240\t\tdevice_type = \"memory\";\n"
  "> > -\t\treg = <0x80000000 0x20000000>;\t/* 512MiB */\n"
  "> > +\t\treg = <0x80000000 0x1f000000>;\t/* 512 - 16 MiB */\n"
  "> Is 16MB fixed size or is this a function of display resolution / density etc.\n"
@@ -33,7 +37,7 @@
  "which gives ~4Mb. Now if we add support of triple-buffering we'll\n"
  "need ~12Mb so I booked a little bit more - 16Mb.\n"
  "\n"
- "But now I recalled that we also support?r8g8b8 mode and in this case\n"
+ "But now I recalled that we also support\302\240r8g8b8 mode and in this case\n"
  "3 bytes are used for color encoding, which effectively gives ~6Mb for\n"
  "1 FullHD frame. And for tripple-buffering we'll need > 18Mb, so probably\n"
  "we'll need to go for 24 or even 32 Mb.\n"
@@ -46,9 +50,9 @@
  "> > +\t\t#size-cells = <1>;\n"
  "> > +\t\tranges;\n"
  "> > +\t\t/*\n"
- "> > +\t\t?* Move frame buffer out of IOC aperture (0x8z-0xAz).\n"
- "> > +\t\t?*/\n"
- "> > +\t\tframe_buffer: frame_buffer at bf000000 {\n"
+ "> > +\t\t\302\240* Move frame buffer out of IOC aperture (0x8z-0xAz).\n"
+ "> > +\t\t\302\240*/\n"
+ "> > +\t\tframe_buffer: frame_buffer@bf000000 {\n"
  "> > +\t\t\tcompatible = \"shared-dma-pool\";\n"
  "> > +\t\t\treg = <0xbf000000 0x1000000>;\n"
  "> Can this be made a bit more future safe. AXS103 has 1 GB of DDR while kernel\n"
@@ -64,4 +68,4 @@
  "\n"
  -Alexey
 
-5d48dc9141f94d82bd33e2488a823618d5909088c631413b84d77d29ec10483a
+37c24e1798574b2191e90902cde8b4096b9c1c553bc5fdf3f7e33429f0557e7e

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.