linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* kernel update on mpc8248 muram definition?
@ 2007-11-15 15:43 Alan Bennett
  2007-11-15 17:30 ` Scott Wood
  0 siblings, 1 reply; 2+ messages in thread
From: Alan Bennett @ 2007-11-15 15:43 UTC (permalink / raw)
  To: Scott Wood, linuxppc-dev

[-- Attachment #1: Type: text/plain, Size: 5063 bytes --]

Hello;

  While working on i2c support, I've decided to update to a new kernel.  In
the process of doing this, I'm not sure I've properly configured the MURAM
node to my device tree (i.e. serial is broken again).  Also, does this, in
any way, change the way I offset the early debug transmit descriptor
address?

  I tried looking at your cpm tree on git.buserror.net, but it seems you've
taken it down?

-Alan

soc@e0000000 {
        #address-cells = <1>;
        #size-cells = <1>;
        device_type = "soc";
        compatible = "fsl,mpc8248", "fsl,pq2-soc";
        ranges = <00000000 e0000000 00053000>;

        // Temporary -- will go away once kernel uses ranges for
get_immrbase().
        reg = <e0000000 00053000>;

        cpm@119c0 {
            #address-cells = <1>;
            #size-cells = <1>;
            compatible = "fsl,mpc8248-cpm", "fsl,cpm2";
                        reg = <119c0 30>;
            ranges;

            muram@0 {
                #address-cells = <1>;
                #size-cells = <1>;
                ranges = <0 0 10000>;

                data@0 {
                    compatible = "fsl,cpm-muram-data";
                    reg = <0 2000 9800 800>;
                };
            };

            brg@119f0 {
                compatible = "fsl,mpc8272-brg",
                         "fsl,cpm2-brg",
                                             "fsl,cpm-brg";
                reg = <119f0 10 115f0 10>;
            };
            /* Monitor port/SMC1 */
            serial@11a80 {
                device_type = "serial";
                compatible = "fsl,mpc8248-smc-uart",
                                             "fsl,cpm2-smc-uart";
                reg = <11a80 20 0 40>;
                interrupts = <4 8>;
                interrupt-parent = <&PIC>;
                fsl,cpm-brg = <7>;
                fsl,cpm-command = <1d000000>;
            };
            /* "Serial" port/SCC1 */
            serial@11a00 {
                device_type = "serial";
                compatible = "fsl,mpc8248-scc-uart",
                                             "fsl,cpm2-scc-uart";
                reg = <11a00 20 8000 100>;
                interrupts = <28 8>;
                interrupt-parent = <&PIC>;
                fsl,cpm-brg = <1>;
                fsl,cpm-command = <00800000>;
                       };
                       /* "Serial" port/SCC4 */
                       serial@11a60 {
                device_type = "serial";
                compatible = "fsl,mpc8248-scc-uart",
                                             "fsl,cpm2-scc-uart";
                reg = <11a60 20 8300 100>;
                interrupts = <2B 8>;
                interrupt-parent = <&PIC>;
                fsl,cpm-brg = <4>;
                fsl,cpm-command = <0CE00000>;
                       };

                       ethernet@11300 {
                               device_type = "network";
                               compatible = "fsl,mpc8248-fcc-enet",
                                            "fsl,cpm2-fcc-enet";
                               reg = <11300 20 8400 100 11390 1>;
                               local-mac-address = [ 00 00 00 00 00 00 ];
                               interrupts = <20 8>;
                               interrupt-parent = <&PIC>;
                               phy-handle = <&PHY0>;
                               linux,network-index = <0>;
                               fsl,cpm-command = <12000300>;
                       };

                       ethernet@11320 {
                               device_type = "network";
                               compatible = "fsl,mpc8248-fcc-enet",
                                            "fsl,cpm2-fcc-enet";
                               reg = <11320 20 8500 100 113b0 1>;
                               local-mac-address = [ 00 00 00 00 00 00 ];
                               interrupts = <21 8>;
                               interrupt-parent = <&PIC>;
                               phy-handle = <&PHY1>;
                               linux,network-index = <1>;
                               fsl,cpm-command = <16200300>;
                       };

                       usb@11b60 {
                               #address-cells = <1>;
                               #size-cells = <0>;
                               compatible = "fsl,mpc8248-usb",
                                            "fsl,cpm2-usb";
                               reg = <11b60 18 8b00 100>;
                               interrupt-parent = <&PIC>;
                               interrupts = <b 8>;
                               fsl,cpm-command = <2e600000>;
                       };
               i2c@11860 {
                   compatible = "fsl,mpc8248-i2c",
                        "fsl,cpm2-i2c",
                        "fsl,cpm-i2c";
                   reg = <11860 20 3c80 30>;
                     interrupts = <1>;
                   interrupt-parent = <&PIC>;
                   fsl,cpm-command = <0010>;
               };

               };

[-- Attachment #2: Type: text/html, Size: 16181 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kernel update on mpc8248 muram definition?
  2007-11-15 15:43 kernel update on mpc8248 muram definition? Alan Bennett
@ 2007-11-15 17:30 ` Scott Wood
  0 siblings, 0 replies; 2+ messages in thread
From: Scott Wood @ 2007-11-15 17:30 UTC (permalink / raw)
  To: Alan Bennett; +Cc: linuxppc-dev

Alan Bennett wrote:
>   While working on i2c support, I've decided to update to a new kernel.  
> In the process of doing this, I'm not sure I've properly configured the 
> MURAM node to my device tree (i.e. serial is broken again).

You haven't -- you copied muram/data/reg from some other tree, rather 
than from resource 2 of cpm/reg in your old tree.

>  Also, does 
> this, in any way, change the way I offset the early debug transmit 
> descriptor address?

No.

>             muram@0 {
>                 #address-cells = <1>;
>                 #size-cells = <1>;
>                 ranges = <0 0 10000>;
> 
>                 data@0 {
>                     compatible = "fsl,cpm-muram-data";
>                     reg = <0 2000 9800 800>;
>                 };
>             };

muram/data/reg should be <80 1f80 9800 800> for your board.

-Scott

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-11-15 17:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-15 15:43 kernel update on mpc8248 muram definition? Alan Bennett
2007-11-15 17:30 ` Scott Wood

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).