diff for duplicates of <20140318201519.GA8637@obsidianresearch.com> diff --git a/a/1.txt b/N1/1.txt index 87d6267..da1aea0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -8,14 +8,14 @@ On Tue, Mar 18, 2014 at 01:02:55PM -0700, Tim Harvey wrote: It is documented in the 'PCI Bus Binding to Open Firware' publication from IEEE. -> >> + pcie at 0,0 { +> >> + pcie@0,0 { > >> + /* 01:00.0 PCIe switch */ > >> + #address-cells = <3>; > >> + #size-cells = <2>; > >> + device_type = "pci"; > >> + reg = <0x0 0 0 0 0>; > >> + -> >> + pcie at 8,0 { +> >> + pcie@8,0 { > > > > What's the naming schema for all these pcie nodes? Generally, we should > > have the numbers encoded in the node name coming from the address cells @@ -44,7 +44,7 @@ which is a fixed property of PCI. > >> + #size-cells = <2>; > >> + device_type = "pci"; > >> + reg = <0x4000 0 0 0 0>; -> >> + eth1: pcie at 0,0 { +> >> + eth1: pcie@0,0 { > >> + /* 08:00.0 GigE */ > >> + #address-cells = <3>; > >> + #size-cells = <2>; @@ -57,3 +57,7 @@ Don't forget your interrupts and interrupt-map - every DT nodes need to describe how its interrupts are routed. Jason +-- +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 9b13087..cf9c1ba 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,15 @@ "ref\01394747064-4106-1-git-send-email-tharvey@gateworks.com\0" "ref\020140314132805.GD813@S2101-09.ap.freescale.net\0" "ref\0CAJ+vNU2Av-n1-efbFbXNvO4SmoobL_WpQKApFRS1Zjy0egLLzw@mail.gmail.com\0" - "From\0jgunthorpe@obsidianresearch.com (Jason Gunthorpe)\0" - "Subject\0[PATCH] ARM: dts: ventana: fix eth1 pci dev node\0" + "ref\0CAJ+vNU2Av-n1-efbFbXNvO4SmoobL_WpQKApFRS1Zjy0egLLzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" + "From\0Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>\0" + "Subject\0Re: [PATCH] ARM: dts: ventana: fix eth1 pci dev node\0" "Date\0Tue, 18 Mar 2014 14:15:19 -0600\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Tim Harvey <tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.org>\0" + "Cc\0Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>" + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0" "\00:1\0" "b\0" "On Tue, Mar 18, 2014 at 01:02:55PM -0700, Tim Harvey wrote:\n" @@ -17,14 +22,14 @@ "It is documented in the 'PCI Bus Binding to Open Firware'\n" "publication from IEEE.\n" "\n" - "> >> + pcie at 0,0 {\n" + "> >> + pcie@0,0 {\n" "> >> + /* 01:00.0 PCIe switch */\n" "> >> + #address-cells = <3>;\n" "> >> + #size-cells = <2>;\n" "> >> + device_type = \"pci\";\n" "> >> + reg = <0x0 0 0 0 0>;\n" "> >> +\n" - "> >> + pcie at 8,0 {\n" + "> >> + pcie@8,0 {\n" "> >\n" "> > What's the naming schema for all these pcie nodes? Generally, we should\n" "> > have the numbers encoded in the node name coming from the address cells\n" @@ -53,7 +58,7 @@ "> >> + #size-cells = <2>;\n" "> >> + device_type = \"pci\";\n" "> >> + reg = <0x4000 0 0 0 0>;\n" - "> >> + eth1: pcie at 0,0 {\n" + "> >> + eth1: pcie@0,0 {\n" "> >> + /* 08:00.0 GigE */\n" "> >> + #address-cells = <3>;\n" "> >> + #size-cells = <2>;\n" @@ -65,6 +70,10 @@ "Don't forget your interrupts and interrupt-map - every DT nodes need\n" "to describe how its interrupts are routed.\n" "\n" - Jason + "Jason\n" + "--\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 -95dba0a865bf98ad72bacf24cb64c966d25a64d4f4d4cf7ddcbe26fddcee248c +972e49c467765afc6206a300f9afbf511ce9b262243b08f675ef869b17854d8a
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.