All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20110630142702.GV23145@atomide.com>

diff --git a/a/1.txt b/N1/1.txt
index 3f26716..184c6df 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -8,23 +8,23 @@ Few comments on the .dts data layout below.
 > @@ -2,11 +2,6 @@
 >  
 >  / {
->  	i2c@48072000 {
+>  	i2c at 48072000 {
 > -		compatible = "ti,omap3-i2c";
 > -		reg = <0x48072000 0x80>;
 > -		#address-cells = <1>;
 > -		#size-cells = <0>;
 > -
->  		eeprom@50 {
+>  		eeprom at 50 {
 >  			compatible = "at,at24c01";
 >  			reg = < 0x50 >;
 
 The board .dts file should include the omap3 SoC .dts file.
 
 The omap3 SoC .dts file should have the devices mapped to L3 and L4
-busses, and the then i2c@1 would just contain the bus offset.
+busses, and the then i2c at 1 would just contain the bus offset.
 
-Then the i2c@1 entry would be repeated in the board specific
-.dts and tell that the i2c@1 is enabled.
+Then the i2c at 1 entry would be repeated in the board specific
+.dts and tell that the i2c at 1 is enabled.
 
 > --- a/arch/arm/boot/dts/omap3-beagle.dts
 > +++ b/arch/arm/boot/dts/omap3-beagle.dts
@@ -34,7 +34,7 @@ Then the i2c@1 entry would be repeated in the board specific
 >  	compatible = "ti,omap3-beagle";
 > +	interrupt-parent = <&gic>;
 > +
-> +	gic: interrupt-controller@48241000 {
+> +	gic: interrupt-controller at 48241000 {
 > +		compatible = "ti,omap-gic", "arm,gic";
 > +		interrupt-controller;
 > +		#interrupt-cells = <1>;
diff --git a/a/content_digest b/N1/content_digest
index 84c547b..4ebeae0 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,15 +1,9 @@
  "ref\01309426647-31587-1-git-send-email-manjugk@ti.com\0"
  "ref\01309426647-31587-2-git-send-email-manjugk@ti.com\0"
- "From\0Tony Lindgren <tony@atomide.com>\0"
- "Subject\0Re: [RFC PATCH 1/5] OMAP3:I2C: Add device tree nodes for beagle board\0"
+ "From\0tony@atomide.com (Tony Lindgren)\0"
+ "Subject\0[RFC PATCH 1/5] OMAP3:I2C: Add device tree nodes for beagle board\0"
  "Date\0Thu, 30 Jun 2011 07:27:02 -0700\0"
- "To\0G"
- " Manjunath Kondaiah <manjugk@ti.com>\0"
- "Cc\0devicetree-discuss@lists.ozlabs.org"
-  linux-arm-kernel@lists.infradead.org
-  linux-omap@vger.kernel.org
-  grant.likely@secretlab.ca
- " ben-linux@fluff.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hi,\n"
@@ -22,23 +16,23 @@
  "> @@ -2,11 +2,6 @@\n"
  ">  \n"
  ">  / {\n"
- ">  \ti2c@48072000 {\n"
+ ">  \ti2c at 48072000 {\n"
  "> -\t\tcompatible = \"ti,omap3-i2c\";\n"
  "> -\t\treg = <0x48072000 0x80>;\n"
  "> -\t\t#address-cells = <1>;\n"
  "> -\t\t#size-cells = <0>;\n"
  "> -\n"
- ">  \t\teeprom@50 {\n"
+ ">  \t\teeprom at 50 {\n"
  ">  \t\t\tcompatible = \"at,at24c01\";\n"
  ">  \t\t\treg = < 0x50 >;\n"
  "\n"
  "The board .dts file should include the omap3 SoC .dts file.\n"
  "\n"
  "The omap3 SoC .dts file should have the devices mapped to L3 and L4\n"
- "busses, and the then i2c@1 would just contain the bus offset.\n"
+ "busses, and the then i2c at 1 would just contain the bus offset.\n"
  "\n"
- "Then the i2c@1 entry would be repeated in the board specific\n"
- ".dts and tell that the i2c@1 is enabled.\n"
+ "Then the i2c at 1 entry would be repeated in the board specific\n"
+ ".dts and tell that the i2c at 1 is enabled.\n"
  "\n"
  "> --- a/arch/arm/boot/dts/omap3-beagle.dts\n"
  "> +++ b/arch/arm/boot/dts/omap3-beagle.dts\n"
@@ -48,7 +42,7 @@
  ">  \tcompatible = \"ti,omap3-beagle\";\n"
  "> +\tinterrupt-parent = <&gic>;\n"
  "> +\n"
- "> +\tgic: interrupt-controller@48241000 {\n"
+ "> +\tgic: interrupt-controller at 48241000 {\n"
  "> +\t\tcompatible = \"ti,omap-gic\", \"arm,gic\";\n"
  "> +\t\tinterrupt-controller;\n"
  "> +\t\t#interrupt-cells = <1>;\n"
@@ -61,4 +55,4 @@
  "\n"
  Tony
 
-1e32a253c3b712a49448205d604a6fc7f6916dffa149fb0077743ff991b6253b
+2b95406227e9fc04cf470f96d9910c352001abd91f0a987b1aef40a5d4ffc1ea

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.