diff for duplicates of <1498754384.2378.10.camel@synopsys.com> diff --git a/a/1.txt b/N1/1.txt index 0265511..2633008 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,10 +1,10 @@ -On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote: -> > > > +???????????????????????#clock-cells = <0>; -> > > > +???????????????????????compatible = "fixed-clock"; -> > > > +???????????????????????clock-frequency = <1000000000>; -> > > > +???????????????}; +On Wed, 2017-06-28 at 17:50 -0500, Rob Herring wrote: +> > > > +                       #clock-cells = <0>; +> > > > +                       compatible = "fixed-clock"; +> > > > +                       clock-frequency = <1000000000>; +> > > > +               }; > > > > + -> > > > +???????????????core_intc: archs-intc at cpu { +> > > > +               core_intc: archs-intc@cpu { > > > > > > cpu is not a valid unit-address. How are these interrupt > > > controllers addressed? @@ -16,37 +16,37 @@ On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote: > > But then we have the next level INTC which is IDU (Interrupt > > Distribution Unit) > > which dispatches "common" IRQs to different upstream per-core INTC, -> > see below its node.? +> > see below its node. > -> Okay, I'd just do "cpu-interrupt-controller" for the node name then.? +> Okay, I'd just do "cpu-interrupt-controller" for the node name then. > There doesn't seem to be an easy way to use just "interrupt- -> controller"? -> since you have 2 nodes at the same level and no unit-address (i.e. a? +> controller" +> since you have 2 nodes at the same level and no unit-address (i.e. a > reg property). > To be more clarify, what is better way do describe such hardware in device tree? --------------????-------------?? -| cpu core 0|????| cpu core 1|?? --------------????-------------?? -| interrupt |????| interrupt |?? -| controller|????| controller|?? -|?????0?????|????|?????1?????|?? --------------????-------------?? -??????^????????????????^ -??????|????????????????| -?????????????----------- -??????|??????| +-------------    -------------  +| cpu core 0|    | cpu core 1|  +-------------    -------------  +| interrupt |    | interrupt |  +| controller|    | controller|  +|     0     |    |     1     |  +-------------    -------------  +      ^                ^ +      |                | +             ----------- +      |      | ---------------- -|???interrupt??| +|   interrupt  | | distribution | -|?????unit?????| +|     unit     | ---------------- -??????^ -??????| -??????|<--other devices interrupt lines +      ^ +      | +      |<--other devices interrupt lines We can't just create a node for each core interrupt controller because we wouldn't able to specify which one is parent for interrupt @@ -54,12 +54,12 @@ distribution unit: ------------>>>------------- cpus { -????cpu at 0 { intc at 0 }; -????cpu at 1 { intc at 1 }; +    cpu@0 { intc@0 }; +    cpu@1 { intc@1 }; }; interrupt-distribution-unit { -????interrupt-parent = ???? +    interrupt-parent = ???? }; ------------>>>------------- @@ -67,4 +67,4 @@ Should we simply create one core interrupt controller node for all cpus (instead of one per each cpu core), or where is a better option? -- -?Eugeniy Paltsev + Eugeniy PaltsevN‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·zøœzÚÞz)í…æèw*\x1fjg¬±¨\x1e¶‰šŽŠÝ¢j.ïÛ°\½½MŽúgjÌæa×\x02››–' ™©Þ¢¸\f¢·¦j:+v‰¨ŠwèjØm¶Ÿÿ¾\a«‘êçzZ+ƒùšŽŠÝ¢j"ú!¶i diff --git a/a/content_digest b/N1/content_digest index 4993f2e..826db24 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,19 +3,25 @@ "ref\0CAL_JsqJBPL+AuYNP=JgXWOGNFxdenKY4Rt3_f6tG6MYDLncRNg@mail.gmail.com\0" "ref\01498494334.28955.58.camel@synopsys.com\0" "ref\020170628225005.5ume54d67vtvp5fi@rob-hp-laptop\0" - "From\0Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)\0" - "Subject\0[PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board\0" + "From\0Eugeniy Paltsev <Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>\0" + "Subject\0Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board\0" "Date\0Thu, 29 Jun 2017 16:39:45 +0000\0" - "To\0linux-snps-arc@lists.infradead.org\0" + "To\0robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" + "Cc\0linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>" + Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org <Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> + Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org <Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> + Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org <Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org> + linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + " devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>\0" "\00:1\0" "b\0" - "On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote:\n" - "> > > > +???????????????????????#clock-cells = <0>;\n" - "> > > > +???????????????????????compatible = \"fixed-clock\";\n" - "> > > > +???????????????????????clock-frequency = <1000000000>;\n" - "> > > > +???????????????};\n" + "On Wed, 2017-06-28 at 17:50 -0500, Rob Herring wrote:\n" + "> > > > +\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240#clock-cells = <0>;\n" + "> > > > +\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240compatible = \"fixed-clock\";\n" + "> > > > +\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240clock-frequency = <1000000000>;\n" + "> > > > +\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240};\n" "> > > > +\n" - "> > > > +???????????????core_intc: archs-intc at cpu {\n" + "> > > > +\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240core_intc: archs-intc@cpu {\n" "> > > \n" "> > > cpu is not a valid unit-address. How are these interrupt\n" "> > > controllers addressed?\n" @@ -27,37 +33,37 @@ "> > But then we have the next level INTC which is IDU (Interrupt\n" "> > Distribution Unit)\n" "> > which dispatches \"common\" IRQs to different upstream per-core INTC,\n" - "> > see below its node.?\n" + "> > see below its node.\303\202\302\240\n" "> \n" - "> Okay, I'd just do \"cpu-interrupt-controller\" for the node name then.?\n" + "> Okay, I'd just do \"cpu-interrupt-controller\" for the node name then.\303\202\302\240\n" "> There doesn't seem to be an easy way to use just \"interrupt-\n" - "> controller\"?\n" - "> since you have 2 nodes at the same level and no unit-address (i.e. a?\n" + "> controller\"\303\202\302\240\n" + "> since you have 2 nodes at the same level and no unit-address (i.e. a\303\202\302\240\n" "> reg property).\n" "> \n" "\n" "To be more clarify, what is better way do describe such hardware in\n" "device tree?\n" "\n" - "-------------????-------------??\n" - "| cpu core 0|????| cpu core 1|??\n" - "-------------????-------------??\n" - "| interrupt |????| interrupt |??\n" - "| controller|????| controller|??\n" - "|?????0?????|????|?????1?????|??\n" - "-------------????-------------??\n" - "??????^????????????????^\n" - "??????|????????????????|\n" - "?????????????-----------\n" - "??????|??????|\n" + "-------------\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240-------------\303\202\302\240\303\202\302\240\n" + "| cpu core 0|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240| cpu core 1|\303\202\302\240\303\202\302\240\n" + "-------------\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240-------------\303\202\302\240\303\202\302\240\n" + "| interrupt |\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240| interrupt |\303\202\302\240\303\202\302\240\n" + "| controller|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240| controller|\303\202\302\240\303\202\302\240\n" + "|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\2400\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\2401\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\303\202\302\240\303\202\302\240\n" + "-------------\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240-------------\303\202\302\240\303\202\302\240\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240^\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240^\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240-----------\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\n" "----------------\n" - "|???interrupt??|\n" + "|\303\202\302\240\303\202\302\240\303\202\302\240interrupt\303\202\302\240\303\202\302\240|\n" "| distribution |\n" - "|?????unit?????|\n" + "|\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240unit\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\n" "----------------\n" - "??????^\n" - "??????|\n" - "??????|<--other devices interrupt lines\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240^\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240|<--other devices interrupt lines\n" "\n" "We can't just create a node for each core interrupt controller because\n" "we wouldn't able to specify which one is parent for interrupt\n" @@ -65,12 +71,12 @@ "\n" "------------>>>-------------\n" "cpus {\n" - "????cpu at 0 { intc at 0 };\n" - "????cpu at 1 { intc at 1 };\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240cpu@0 { intc@0 };\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240cpu@1 { intc@1 };\n" "};\n" "\n" "interrupt-distribution-unit {\n" - "????interrupt-parent = ????\n" + "\303\202\302\240\303\202\302\240\303\202\302\240\303\202\302\240interrupt-parent = ????\n" "};\n" "------------>>>-------------\n" "\n" @@ -78,6 +84,6 @@ "(instead of one per each cpu core), or where is a better option?\n" "\n" "-- \n" - ?Eugeniy Paltsev + "\303\202\302\240Eugeniy PaltsevN\302\213\302\247\302\262\303\246\303\254r\302\270\302\233y\303\272\303\250\302\232\303\230b\302\262X\302\254\302\266\303\207\302\247v\303\230^\302\226)\303\236\302\272{.n\303\207+\302\211\302\267\302\235z\303\270\302\234z\303\232\303\236z)\303\255\302\205\303\246\303\250w*\037jg\302\254\302\261\302\250\036\302\266\302\211\302\232\302\216\302\212\303\235\302\242j.\303\257\303\233\302\260\\\302\275\302\275M\302\216\303\272gj\303\214\303\246a\303\227\002\302\233\302\233\302\226' \302\231\302\251\303\236\302\242\302\270\f\302\242\302\267\302\246j:+v\302\211\302\250\302\212w\303\250j\303\230m\302\266\302\237\303\277\302\276\a\302\253\302\221\303\252\303\247zZ+\302\203\303\271\302\232\302\216\302\212\303\235\302\242j\"\302\235\303\272!\302\266i" -3ce5b08ea5374f85dcf40b9c09bbf917ca9bc307b26575bc0ee129782bffe890 +e1286306b45e55821c911fb7f19847249dd8249b3ed6715941609c9323711a41
diff --git a/a/1.txt b/N2/1.txt index 0265511..3b40d60 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,10 +1,10 @@ -On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote: -> > > > +???????????????????????#clock-cells = <0>; -> > > > +???????????????????????compatible = "fixed-clock"; -> > > > +???????????????????????clock-frequency = <1000000000>; -> > > > +???????????????}; +On Wed, 2017-06-28 at 17:50 -0500, Rob Herring wrote: +> > > > + #clock-cells = <0>; +> > > > + compatible = "fixed-clock"; +> > > > + clock-frequency = <1000000000>; +> > > > + }; > > > > + -> > > > +???????????????core_intc: archs-intc at cpu { +> > > > + core_intc: archs-intc@cpu { > > > > > > cpu is not a valid unit-address. How are these interrupt > > > controllers addressed? @@ -16,37 +16,37 @@ On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote: > > But then we have the next level INTC which is IDU (Interrupt > > Distribution Unit) > > which dispatches "common" IRQs to different upstream per-core INTC, -> > see below its node.? +> > see below its node. > -> Okay, I'd just do "cpu-interrupt-controller" for the node name then.? +> Okay, I'd just do "cpu-interrupt-controller" for the node name then. > There doesn't seem to be an easy way to use just "interrupt- -> controller"? -> since you have 2 nodes at the same level and no unit-address (i.e. a? +> controller" +> since you have 2 nodes at the same level and no unit-address (i.e. a > reg property). > To be more clarify, what is better way do describe such hardware in device tree? --------------????-------------?? -| cpu core 0|????| cpu core 1|?? --------------????-------------?? -| interrupt |????| interrupt |?? -| controller|????| controller|?? -|?????0?????|????|?????1?????|?? --------------????-------------?? -??????^????????????????^ -??????|????????????????| -?????????????----------- -??????|??????| +------------- ------------- +| cpu core 0| | cpu core 1| +------------- ------------- +| interrupt | | interrupt | +| controller| | controller| +| 0 | | 1 | +------------- ------------- + ^ ^ + | | + ----------- + | | ---------------- -|???interrupt??| +| interrupt | | distribution | -|?????unit?????| +| unit | ---------------- -??????^ -??????| -??????|<--other devices interrupt lines + ^ + | + |<--other devices interrupt lines We can't just create a node for each core interrupt controller because we wouldn't able to specify which one is parent for interrupt @@ -54,12 +54,12 @@ distribution unit: ------------>>>------------- cpus { -????cpu at 0 { intc at 0 }; -????cpu at 1 { intc at 1 }; + cpu@0 { intc@0 }; + cpu@1 { intc@1 }; }; interrupt-distribution-unit { -????interrupt-parent = ???? + interrupt-parent = ???? }; ------------>>>------------- @@ -67,4 +67,4 @@ Should we simply create one core interrupt controller node for all cpus (instead of one per each cpu core), or where is a better option? -- -?Eugeniy Paltsev + Eugeniy Paltsev diff --git a/a/content_digest b/N2/content_digest index 4993f2e..65e5b7d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,19 +3,25 @@ "ref\0CAL_JsqJBPL+AuYNP=JgXWOGNFxdenKY4Rt3_f6tG6MYDLncRNg@mail.gmail.com\0" "ref\01498494334.28955.58.camel@synopsys.com\0" "ref\020170628225005.5ume54d67vtvp5fi@rob-hp-laptop\0" - "From\0Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)\0" - "Subject\0[PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board\0" + "From\0Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>\0" + "Subject\0Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board\0" "Date\0Thu, 29 Jun 2017 16:39:45 +0000\0" - "To\0linux-snps-arc@lists.infradead.org\0" + "To\0robh@kernel.org <robh@kernel.org>\0" + "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>" + Vineet.Gupta1@synopsys.com <Vineet.Gupta1@synopsys.com> + Eugeniy.Paltsev@synopsys.com <Eugeniy.Paltsev@synopsys.com> + Alexey.Brodkin@synopsys.com <Alexey.Brodkin@synopsys.com> + linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org> + " devicetree@vger.kernel.org <devicetree@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Wed, 2017-06-28@17:50 -0500, Rob Herring wrote:\n" - "> > > > +???????????????????????#clock-cells = <0>;\n" - "> > > > +???????????????????????compatible = \"fixed-clock\";\n" - "> > > > +???????????????????????clock-frequency = <1000000000>;\n" - "> > > > +???????????????};\n" + "On Wed, 2017-06-28 at 17:50 -0500, Rob Herring wrote:\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#clock-cells = <0>;\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\240compatible = \"fixed-clock\";\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\240clock-frequency = <1000000000>;\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};\n" "> > > > +\n" - "> > > > +???????????????core_intc: archs-intc at cpu {\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\240core_intc: archs-intc@cpu {\n" "> > > \n" "> > > cpu is not a valid unit-address. How are these interrupt\n" "> > > controllers addressed?\n" @@ -27,37 +33,37 @@ "> > But then we have the next level INTC which is IDU (Interrupt\n" "> > Distribution Unit)\n" "> > which dispatches \"common\" IRQs to different upstream per-core INTC,\n" - "> > see below its node.?\n" + "> > see below its node.\302\240\n" "> \n" - "> Okay, I'd just do \"cpu-interrupt-controller\" for the node name then.?\n" + "> Okay, I'd just do \"cpu-interrupt-controller\" for the node name then.\302\240\n" "> There doesn't seem to be an easy way to use just \"interrupt-\n" - "> controller\"?\n" - "> since you have 2 nodes at the same level and no unit-address (i.e. a?\n" + "> controller\"\302\240\n" + "> since you have 2 nodes at the same level and no unit-address (i.e. a\302\240\n" "> reg property).\n" "> \n" "\n" "To be more clarify, what is better way do describe such hardware in\n" "device tree?\n" "\n" - "-------------????-------------??\n" - "| cpu core 0|????| cpu core 1|??\n" - "-------------????-------------??\n" - "| interrupt |????| interrupt |??\n" - "| controller|????| controller|??\n" - "|?????0?????|????|?????1?????|??\n" - "-------------????-------------??\n" - "??????^????????????????^\n" - "??????|????????????????|\n" - "?????????????-----------\n" - "??????|??????|\n" + "-------------\302\240\302\240\302\240\302\240-------------\302\240\302\240\n" + "| cpu core 0|\302\240\302\240\302\240\302\240| cpu core 1|\302\240\302\240\n" + "-------------\302\240\302\240\302\240\302\240-------------\302\240\302\240\n" + "| interrupt |\302\240\302\240\302\240\302\240| interrupt |\302\240\302\240\n" + "| controller|\302\240\302\240\302\240\302\240| controller|\302\240\302\240\n" + "|\302\240\302\240\302\240\302\240\302\2400\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\2401\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\n" + "-------------\302\240\302\240\302\240\302\240-------------\302\240\302\240\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^\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|\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-----------\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|\n" "----------------\n" - "|???interrupt??|\n" + "|\302\240\302\240\302\240interrupt\302\240\302\240|\n" "| distribution |\n" - "|?????unit?????|\n" + "|\302\240\302\240\302\240\302\240\302\240unit\302\240\302\240\302\240\302\240\302\240|\n" "----------------\n" - "??????^\n" - "??????|\n" - "??????|<--other devices interrupt lines\n" + "\302\240\302\240\302\240\302\240\302\240\302\240^\n" + "\302\240\302\240\302\240\302\240\302\240\302\240|\n" + "\302\240\302\240\302\240\302\240\302\240\302\240|<--other devices interrupt lines\n" "\n" "We can't just create a node for each core interrupt controller because\n" "we wouldn't able to specify which one is parent for interrupt\n" @@ -65,12 +71,12 @@ "\n" "------------>>>-------------\n" "cpus {\n" - "????cpu at 0 { intc at 0 };\n" - "????cpu at 1 { intc at 1 };\n" + "\302\240\302\240\302\240\302\240cpu@0 { intc@0 };\n" + "\302\240\302\240\302\240\302\240cpu@1 { intc@1 };\n" "};\n" "\n" "interrupt-distribution-unit {\n" - "????interrupt-parent = ????\n" + "\302\240\302\240\302\240\302\240interrupt-parent = ????\n" "};\n" "------------>>>-------------\n" "\n" @@ -78,6 +84,6 @@ "(instead of one per each cpu core), or where is a better option?\n" "\n" "-- \n" - ?Eugeniy Paltsev + "\302\240Eugeniy Paltsev" -3ce5b08ea5374f85dcf40b9c09bbf917ca9bc307b26575bc0ee129782bffe890 +26a47c8043e841bba5577ac100c8113dc5244f1650f7f09072676e41e5f1b092
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.