From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc1-s36.bay0.hotmail.com (bay0-omc1-s36.bay0.hotmail.com [65.54.246.108]) by ozlabs.org (Postfix) with ESMTP id 60AE1DDEDF for ; Wed, 7 May 2008 07:10:37 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_20cc832d-76ed-49b8-bd53-d337c0ac5d43_" From: Ronald Madrid To: Subject: ifconfig MPC8313 Date: Tue, 6 May 2008 14:10:36 -0700 MIME-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_20cc832d-76ed-49b8-bd53-d337c0ac5d43_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello all, I am working on porting linux 2.6.25 with a custom MPC8313 based board, but= am having a little bit of trouble with the ethernet, more specifically ifc= onfig. after typing "ifconfig eth0 10.196.31.84" I receive the following error ifconfig: SIOCSIFFLAGS: Cannot assign requested address after entering a MAC address via "ifconfig eth0 hw ether" I receive this e= rror. e0024520:01 not found eth0: Could not attach to PHY ifconfig: SIOCSIFFLAGS: No such device which I have traced to bus_find_device, but I'm not sure what to make of th= is. I'm not sure where I'm going wrong here, and I'm sure that it's something t= hat I'm forgetting to do/include. Sorry if this isn't enough information, but I don't know enough to know wha= t other information would be needed. Ron _________________________________________________________________ Get Free (PRODUCT) RED=99 Emoticons, Winks and Display Pics. http://joinred.spaces.live.com?ocid=3DTXT_HMTG_prodredemoticons_052008= --_20cc832d-76ed-49b8-bd53-d337c0ac5d43_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello all,
I am working on porting linux 2.6.25 with a custom MPC8313 based board, b= ut am having a little bit of trouble with the ethernet, more specifically i= fconfig.

after typing "ifconfig eth0 10.196.31.84" I receive the fol= lowing error
ifconfig: SIOCSIFFLAGS: Cannot assign requested address
=
after entering a MAC address via "ifconfig eth0 hw ether"  I recei= ve this error.
e0024520:01 not found
eth0: Could not attach to PHYifconfig: SIOCSIFFLAGS: No such device

which I have traced to bus_f= ind_device, but I'm not sure what to make of this.

I'm not sure wher= e I'm going wrong here, and I'm sure that it's something that I'm forgettin= g to do/include.

Sorry if this isn't enough information, but I don't= know enough to know what other information would be needed.

<= br>Ron


Get Free (PRODUCT) RED=99 Emoticons, Winks and Displ= ay Pics. Check it out! = --_20cc832d-76ed-49b8-bd53-d337c0ac5d43_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id E39CFDDF49 for ; Wed, 7 May 2008 07:18:37 +1000 (EST) Message-ID: <4820CB5D.3000703@freescale.com> Date: Tue, 06 May 2008 16:19:25 -0500 From: Scott Wood MIME-Version: 1.0 To: Ronald Madrid Subject: Re: ifconfig MPC8313 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ronald Madrid wrote: > Hello all, > > I am working on porting linux 2.6.25 with a custom MPC8313 based board, > but am having a little bit of trouble with the ethernet, more > specifically ifconfig. > > after typing "ifconfig eth0 10.196.31.84" I receive the following error > ifconfig: SIOCSIFFLAGS: Cannot assign requested address > > after entering a MAC address via "ifconfig eth0 hw ether" I receive > this error. > e0024520:01 not found > eth0: Could not attach to PHY > ifconfig: SIOCSIFFLAGS: No such device It can't find the PHY for eth0. What does your device tree look like, and what is the relevant PHY address? -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc3-s22.bay0.hotmail.com (bay0-omc3-s22.bay0.hotmail.com [65.54.246.222]) by ozlabs.org (Postfix) with ESMTP id 752FFDDF7F for ; Wed, 7 May 2008 07:24:49 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_05e3a848-ba53-45af-866c-d19a689830c5_" From: Ronald Madrid To: Scott Wood Subject: RE: ifconfig MPC8313 Date: Tue, 6 May 2008 14:24:48 -0700 In-Reply-To: <4820CB5D.3000703@freescale.com> References: <4820CB5D.3000703@freescale.com> MIME-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_05e3a848-ba53-45af-866c-d19a689830c5_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm guessing by device tree you mean the .dts file? I'm using a modified v= ersion of the mpc8313erdb.dts with minor changes (to the local bus only). = Here is a copy of it./* * MPC8313E RDB Device Tree Source * * Copyright 200= 5, 2006, 2007 Freescale Semiconductor Inc. * * This program is free softwar= e; you can redistribute it and/or modify it * under the terms of the GNU= General Public License as published by the * Free Software Foundation; e= ither version 2 of the License, or (at your * option) any later version. *= //dts-v1/;/ { model =3D "MPC8313ERDB"; compatible =3D "MPC8313ERDB", = "MPC831xRDB", "MPC83xxRDB"; #address-cells =3D <1>; #size-cells =3D <= 1>; aliases { ethernet0 =3D &enet0; ethernet1 =3D &enet1; = serial0 =3D &serial0; serial1 =3D &serial1; pci0 =3D &= pci0; }; cpus { #address-cells =3D <1>; #size-cells =3D= <0>; PowerPC,8313@0 { device_type =3D "cpu"; = reg =3D <0x0>; d-cache-line-size =3D <32>; i-cache-li= ne-size =3D <32>; d-cache-size =3D <16384>; i-cache-s= ize =3D <16384>; timebase-frequency =3D <0>; // from bootload= er bus-frequency =3D <0>; // from bootloader c= lock-frequency =3D <0>; // from bootloader }; }; memory= { device_type =3D "memory"; reg =3D <0x00000000 0x08000000>;= // 128MB at 0 }; localbus@e0005000 { #address-cells =3D <2= >; #size-cells =3D <1>; compatible =3D "fsl,mpc8313-elbc", "f= sl,elbc", "simple-bus"; reg =3D <0xe0005000 0x1000>; interrup= ts =3D <77 0x8>; interrupt-parent =3D <&ipic>; // CS0 and CS1= are swapped when // booting from nand, but the // addresses = are the same.// ranges =3D <0x0 0x0 0xfe000000 0x00800000// = 0x1 0x0 0xe2800000 0x00008000// 0x2 0x0 0xf000000= 0 0x00020000// 0x3 0x0 0xfa000000 0x00008000>; rang= es =3D <0x0 0x0 0xe2800000 0x00008000>;// flash@0,0 {// #= address-cells =3D <1>;// #size-cells =3D <1>;// compa= tible =3D "cfi-flash";// reg =3D <0x0 0x0 0x800000>;// = bank-width =3D <2>;// device-width =3D <1>;// };// = nand@1,0 { nand@0,0 { #address-cells =3D <1>; = #size-cells =3D <1>; compatible =3D "fsl,mpc8313-fcm-nand", = "fsl,elbc-fcm-nand";// reg =3D <0x1 0x0 0= x2000>; reg =3D <0x0 0x0 0x2000>; u-boot@0 { = reg =3D <0x0 0x100000>; read-only; }; = kernel@100000 { reg =3D <0x100000 0x300000>; = }; fs@400000 { reg =3D <0x400000 0x1c00000>; = }; }; }; soc8313@e0000000 { #address-cells = =3D <1>; #size-cells =3D <1>; device_type =3D "soc"; c= ompatible =3D "simple-bus"; ranges =3D <0x0 0xe0000000 0x00100000>; = reg =3D <0xe0000000 0x00000200>; bus-frequency =3D <0>; = wdt@200 { device_type =3D "watchdog"; compatible = =3D "mpc83xx_wdt"; reg =3D <0x200 0x100>; }; i2c@3= 000 { #address-cells =3D <1>; #size-cells =3D <0>; = cell-index =3D <0>; compatible =3D "fsl-i2c"; = reg =3D <0x3000 0x100>; interrupts =3D <14 0x8>; in= terrupt-parent =3D <&ipic>; dfsrr; rtc@68 { = compatible =3D "dallas,ds1339"; reg =3D <0x68>; = }; }; i2c@3100 { #address-cells =3D <1>; = #size-cells =3D <0>; cell-index =3D <1>; compa= tible =3D "fsl-i2c"; reg =3D <0x3100 0x100>; interrup= ts =3D <15 0x8>; interrupt-parent =3D <&ipic>; dfsrr;= }; spi@7000 { cell-index =3D <0>; comp= atible =3D "fsl,spi"; reg =3D <0x7000 0x1000>; interr= upts =3D <16 0x8>; interrupt-parent =3D <&ipic>; mode= =3D "cpu"; }; /* phy type (ULPI, UTMI, UTMI_WIDE, SERIAL) */= usb@23000 { compatible =3D "fsl-usb2-dr"; reg= =3D <0x23000 0x1000>; #address-cells =3D <1>; #size-= cells =3D <0>; interrupt-parent =3D <&ipic>; interrup= ts =3D <38 0x8>; phy_type =3D "utmi_wide"; }; mdio= @24520 { #address-cells =3D <1>; #size-cells =3D <0>;= compatible =3D "fsl,gianfar-mdio"; reg =3D <0x24520 = 0x20>; phy1: ethernet-phy@1 { interrupt-parent = =3D <&ipic>; interrupts =3D <19 0x8>; reg =3D= <0x1>; device_type =3D "ethernet-phy"; }; = phy4: ethernet-phy@4 { interrupt-parent =3D <&ipic>; = interrupts =3D <20 0x8>; reg =3D <0x4>; = device_type =3D "ethernet-phy"; }; }; enet= 0: ethernet@24000 { cell-index =3D <0>; device_type = =3D "network"; model =3D "eTSEC"; compatible =3D "gia= nfar"; reg =3D <0x24000 0x1000>; local-mac-address = =3D [ 00 00 00 00 00 00 ]; interrupts =3D <37 0x8 36 0x8 35 0x8>= ; interrupt-parent =3D <&ipic>; phy-handle =3D < &phy= 1 >; }; enet1: ethernet@25000 { cell-index =3D <1>= ; device_type =3D "network"; model =3D "eTSEC"; = compatible =3D "gianfar"; reg =3D <0x25000 0x1000>; = local-mac-address =3D [ 00 00 00 00 00 00 ]; interrupts =3D= <34 0x8 33 0x8 32 0x8>; interrupt-parent =3D <&ipic>; = phy-handle =3D < &phy4 >; }; serial0: serial@4500 { = cell-index =3D <0>; device_type =3D "serial"; com= patible =3D "ns16550"; reg =3D <0x4500 0x100>; clock-= frequency =3D <0>; interrupts =3D <9 0x8>; interrupt-= parent =3D <&ipic>; }; serial1: serial@4600 { cell= -index =3D <1>; device_type =3D "serial"; compatible = =3D "ns16550"; reg =3D <0x4600 0x100>; clock-frequenc= y =3D <0>; interrupts =3D <10 0x8>; interrupt-parent = =3D <&ipic>; }; crypto@30000 { device_type =3D "cr= ypto"; model =3D "SEC2"; compatible =3D "talitos"; = reg =3D <0x30000 0x7000>; interrupts =3D <11 0x8>; = interrupt-parent =3D <&ipic>; /* Rev. 2.2 */ n= um-channels =3D <1>; channel-fifo-len =3D <24>; exec-= units-mask =3D <0x0000004c>; descriptor-types-mask =3D <0x012200= 3f>; }; /* IPIC * interrupts cell =3D = * sense values match linux IORESOURCE_IRQ_* defines: * sen= se =3D=3D 8: Level, low assertion * sense =3D=3D 2: Edge, high-to-l= ow change */ ipic: pic@700 { interrupt-controller= ; #address-cells =3D <0>; #interrupt-cells =3D <2>; = reg =3D <0x700 0x100>; device_type =3D "ipic"; = }; }; pci0: pci@e0008500 { cell-index =3D <1>; interrup= t-map-mask =3D <0xf800 0x0 0x0 0x7>; interrupt-map =3D < = /* IDSEL 0x0E -mini PCI */ 0x7000 0x0 0x0 0x1 &ipic 18 = 0x8 0x7000 0x0 0x0 0x2 &ipic 18 0x8 0x7000 = 0x0 0x0 0x3 &ipic 18 0x8 0x7000 0x0 0x0 0x4 &ipic 18 0x8 = /* IDSEL 0x0F - PCI slot */ 0x7800 0x0 0x0 0x1= &ipic 17 0x8 0x7800 0x0 0x0 0x2 &ipic 18 0x8 = 0x7800 0x0 0x0 0x3 &ipic 17 0x8 0x7800 0x0 0x0 0x4 &ipic= 18 0x8>; interrupt-parent =3D <&ipic>; interrupts =3D <66 0x= 8>; bus-range =3D <0x0 0x0>; ranges =3D <0x02000000 0x0 0x900= 00000 0x90000000 0x0 0x10000000 0x42000000 0x0 0x80000000 0x80= 000000 0x0 0x10000000 0x01000000 0x0 0x00000000 0xe2000000 0x0= 0x00100000>; clock-frequency =3D <66666666>; #interrupt-cell= s =3D <1>; #size-cells =3D <2>; #address-cells =3D <3>; = reg =3D <0xe0008500 0x100>; compatible =3D "fsl,mpc8349-pci"; = device_type =3D "pci"; };};Ron> Date: Tue, 6 May 2008 16:19:25 -0500>= From: scottwood@freescale.com> To: ron_madrid@hotmail.com> CC: linuxppc-de= v@ozlabs.org> Subject: Re: ifconfig MPC8313> > Ronald Madrid wrote:> > Hell= o all,> > > > I am working on porting linux 2.6.25 with a custom MPC8313 ba= sed board, > > but am having a little bit of trouble with the ethernet, mor= e > > specifically ifconfig.> > > > after typing "ifconfig eth0 10.196.31.8= 4" I receive the following error> > ifconfig: SIOCSIFFLAGS: Cannot assign r= equested address> > > > after entering a MAC address via "ifconfig eth0 hw = ether" I receive > > this error.> > e0024520:01 not found> > eth0: Could n= ot attach to PHY> > ifconfig: SIOCSIFFLAGS: No such device> > It can't find= the PHY for eth0. What does your device tree look like, > and what is the= relevant PHY address?> > -Scott _________________________________________________________________ Windows Live SkyDrive lets you share files with faraway friends. http://www.windowslive.com/skydrive/overview.html?ocid=3DTXT_TAGLM_WL_Refre= sh_skydrive_052008= --_05e3a848-ba53-45af-866c-d19a689830c5_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm guessing by = device tree you mean the .dts file?  I'm using a modified version of t= he mpc8313erdb.dts with minor changes (to the local bus only).  Here i= s a copy of it.

/*
 * MPC8313E RDB Device Tree Source
&nb= sp;*
 * Copyright 2005, 2006, 2007 Freescale Semiconductor Inc.
=  *
 * This program is free software; you can redistribute = ; it and/or modify it
 * under  the terms of  the GNU Gen= eral  Public License as published by the
 * Free Software Foun= dation;  either version 2 of the  License, or (at your
 *= option) any later version.
 */

/dts-v1/;

/ {
&nbs= p;   model =3D "MPC8313ERDB";
    compatible = =3D "MPC8313ERDB", "MPC831xRDB", "MPC83xxRDB";
    #addre= ss-cells =3D <1>;
    #size-cells =3D <1>;
    aliases {
        = ethernet0 =3D &enet0;
        ethernet= 1 =3D &enet1;
        serial0 =3D &= ;serial0;
        serial1 =3D &serial1= ;
        pci0 =3D &pci0;
 &nb= sp;  };

    cpus {
     &= nbsp;  #address-cells =3D <1>;
      = ;  #size-cells =3D <0>;

      &n= bsp; PowerPC,8313@0 {
          =   device_type =3D "cpu";
        &nbs= p;   reg =3D <0x0>;
       = ;     d-cache-line-size =3D <32>;
   = ;         i-cache-line-size =3D <32>;            d-cache-size =3D= <16384>;
           = i-cache-size =3D <16384>;
        &= nbsp;   timebase-frequency =3D <0>;    // fr= om bootloader
            b= us-frequency =3D <0>;        // from bo= otloader
            clock-= frequency =3D <0>;        // from bootl= oader
        };
    };<= br>
    memory {
       = device_type =3D "memory";
        reg =3D= <0x00000000 0x08000000>;    // 128MB at 0
 &n= bsp;  };

    localbus@e0005000 {
  =       #address-cells =3D <2>;
  &nbs= p;     #size-cells =3D <1>;
    &nbs= p;   compatible =3D "fsl,mpc8313-elbc", "fsl,elbc", "simple-bus";=
        reg =3D <0xe0005000 0x1000>= ;
        interrupts =3D <77 0x8>;        interrupt-parent =3D <&ipic&= gt;;

        // CS0 and CS1 are swappe= d when
        // booting from nand, but t= he
        // addresses are the same.
/= /        ranges =3D <0x0 0x0 0xfe000000 0x= 00800000
//            = ;      0x1 0x0 0xe2800000 0x00008000
// &n= bsp;             &nb= sp;  0x2 0x0 0xf0000000 0x00020000
//      = ;            0x3 0x0 0xfa= 000000 0x00008000>;
        ranges =3D = <0x0 0x0 0xe2800000 0x00008000>;

//     &n= bsp;  flash@0,0 {
//         &nb= sp;  #address-cells =3D <1>;
//      = ;      #size-cells =3D <1>;
//  &nbs= p;         compatible =3D "cfi-flash";
//&= nbsp;           reg =3D <0x0 0x0= 0x800000>;
//           = ; bank-width =3D <2>;
//        &nbs= p;   device-width =3D <1>;
//     &n= bsp;  };

//        nand@1,0 {
=         nand@0,0 {
    &nbs= p;       #address-cells =3D <1>;
 &n= bsp;          #size-cells =3D <1>;=
            compatible =3D= "fsl,mpc8313-fcm-nand",
         &nb= sp;             = ;  "fsl,elbc-fcm-nand";
//        &nb= sp;   reg =3D <0x1 0x0 0x2000>;
     = ;       reg =3D <0x0 0x0 0x2000>;

&nb= sp;           u-boot@0 {
 &= nbsp;              reg = =3D <0x0 0x100000>;
         &n= bsp;      read-only;
      =       };

        &= nbsp;   kernel@100000 {
        =         reg =3D <0x100000 0x300000>;            };

 &= nbsp;          fs@400000 {
 &nbs= p;              reg =3D &= lt;0x400000 0x1c00000>;
         &= nbsp;  };
        };
  &= nbsp; };

    soc8313@e0000000 {
   =     #address-cells =3D <1>;
    &nb= sp;   #size-cells =3D <1>;
     &nbs= p;  device_type =3D "soc";
        co= mpatible =3D "simple-bus";
        ranges = =3D <0x0 0xe0000000 0x00100000>;
      &n= bsp; reg =3D <0xe0000000 0x00000200>;
     &nb= sp;  bus-frequency =3D <0>;

     &nbs= p;  wdt@200 {
          &nb= sp; device_type =3D "watchdog";
        &n= bsp;   compatible =3D "mpc83xx_wdt";
     =        reg =3D <0x200 0x100>;
  = ;      };

        = i2c@3000 {
            #add= ress-cells =3D <1>;
         &n= bsp;  #size-cells =3D <0>;
      &nb= sp;     cell-index =3D <0>;
    &nbs= p;       compatible =3D "fsl-i2c";
  =           reg =3D <0x3000 0x100>;<= br>            interrupts =3D = <14 0x8>;
           = interrupt-parent =3D <&ipic>;
      =       dfsrr;
        &= nbsp;   rtc@68 {
         &= nbsp;      compatible =3D "dallas,ds1339";
 &nb= sp;              reg =3D = <0x68>;
            }= ;
        };

    &nb= sp;   i2c@3100 {
         &= nbsp;  #address-cells =3D <1>;
      = ;      #size-cells =3D <0>;
   =         cell-index =3D <1>;
 &= nbsp;          compatible =3D "fsl-i2c";=
            reg =3D <0x= 3100 0x100>;
           = interrupts =3D <15 0x8>;
        &n= bsp;   interrupt-parent =3D <&ipic>;
  &nb= sp;         dfsrr;
    &nbs= p;   };

        spi@7000 {            cell-index =3D &= lt;0>;
            compa= tible =3D "fsl,spi";
          &= nbsp; reg =3D <0x7000 0x1000>;
      &nbs= p;     interrupts =3D <16 0x8>;
    =         interrupt-parent =3D <&ipic>= ;;
            mode =3D "cp= u";
        };

    &= nbsp;   /* phy type (ULPI, UTMI, UTMI_WIDE, SERIAL) */
 &= nbsp;      usb@23000 {
     &nbs= p;      compatible =3D "fsl-usb2-dr";
  &n= bsp;         reg =3D <0x23000 0x1000>;<= br>            #address-cells = =3D <1>;
            = #size-cells =3D <0>;
         &= nbsp;  interrupt-parent =3D <&ipic>;
    &= nbsp;       interrupts =3D <38 0x8>;
&nbs= p;           phy_type =3D "utmi_wid= e";
        };

    &= nbsp;   mdio@24520 {
        &nb= sp;   #address-cells =3D <1>;
     &= nbsp;      #size-cells =3D <0>;
  &n= bsp;         compatible =3D "fsl,gianfar-mdio= ";
            reg =3D <= 0x24520 0x20>;
          &nbs= p; phy1: ethernet-phy@1 {
         &n= bsp;      interrupt-parent =3D <&ipic>;
&n= bsp;               i= nterrupts =3D <19 0x8>;
        &nbs= p;       reg =3D <0x1>;
   = ;             device_type =3D = "ethernet-phy";
           = };
            phy4: ether= net-phy@4 {
            &nb= sp;   interrupt-parent =3D <&ipic>;
  &nbs= p;             interrupts =3D = <20 0x8>;
           =     reg =3D <0x4>;
      =           device_type =3D "ethernet-phy"= ;
            };
 &= nbsp;      };

      &nb= sp; enet0: ethernet@24000 {
         =    cell-index =3D <0>;
      &n= bsp;     device_type =3D "network";
    &n= bsp;       model =3D "eTSEC";
   = ;         compatible =3D "gianfar";
 =            reg =3D <0x24000 0x10= 00>;
            local-m= ac-address =3D [ 00 00 00 00 00 00 ];
      &nb= sp;     interrupts =3D <37 0x8 36 0x8 35 0x8>;
&nbs= p;           interrupt-parent =3D &= lt;&ipic>;
          &nbs= p; phy-handle =3D < &phy1 >;
      &n= bsp; };

        enet1: ethernet@25000 = {
            cell-index = =3D <1>;
            = device_type =3D "network";
         &= nbsp;  model =3D "eTSEC";
        &nb= sp;   compatible =3D "gianfar";
      = ;      reg =3D <0x25000 0x1000>;
  &= nbsp;         local-mac-address =3D [ 00 00 0= 0 00 00 00 ];
            i= nterrupts =3D <34 0x8 33 0x8 32 0x8>;
     &nb= sp;      interrupt-parent =3D <&ipic>;
&nb= sp;           phy-handle =3D < &= amp;phy4 >;
        };

 &nb= sp;      serial0: serial@4500 {
    &= nbsp;       cell-index =3D <0>;
 &nb= sp;          device_type =3D "serial";            compatible =3D "= ns16550";
            reg = =3D <0x4500 0x100>;
         &n= bsp;  clock-frequency =3D <0>;
      = ;      interrupts =3D <9 0x8>;
  &nb= sp;         interrupt-parent =3D <&ipi= c>;
        };

   = ;     serial1: serial@4600 {
     &nb= sp;      cell-index =3D <1>;
   = ;         device_type =3D "serial";
 =            compatible =3D "ns16550"= ;
            reg =3D <0= x4600 0x100>;
           = ; clock-frequency =3D <0>;
        &= nbsp;   interrupts =3D <10 0x8>;
    &nbs= p;       interrupt-parent =3D <&ipic>;        };

     =    crypto@30000 {
         =    device_type =3D "crypto";
      &n= bsp;     model =3D "SEC2";
      = ;      compatible =3D "talitos";
    =         reg =3D <0x30000 0x7000>;
&n= bsp;           interrupts =3D <1= 1 0x8>;
            inte= rrupt-parent =3D <&ipic>;
       = ;     /* Rev. 2.2 */
       = ;     num-channels =3D <1>;
    &nbs= p;       channel-fifo-len =3D <24>;
 = ;           exec-units-mask =3D <= ;0x0000004c>;
           = ; descriptor-types-mask =3D <0x0122003f>;
     = ;   };

        /* IPIC
&n= bsp;        * interrupts cell =3D <intr #,= sense>
         * sense values ma= tch linux IORESOURCE_IRQ_* defines:
       = ;  * sense =3D=3D 8: Level, low assertion
     =     * sense =3D=3D 2: Edge, high-to-low change
 &nbs= p;       */
      &nbs= p; ipic: pic@700 {
          &nb= sp; interrupt-controller;
         &n= bsp;  #address-cells =3D <0>;
      =       #interrupt-cells =3D <2>;
  &n= bsp;         reg =3D <0x700 0x100>;
=             device_type =3D "i= pic";
        };
    };<= br>
    pci0: pci@e0008500 {
     =    cell-index =3D <1>;
      &n= bsp; interrupt-map-mask =3D <0xf800 0x0 0x0 0x7>;
  &nbs= p;     interrupt-map =3D <

    &nbs= p;           /* IDSEL 0x0E -mini PC= I */
             &nbs= p;   0x7000 0x0 0x0 0x1 &ipic 18 0x8
    &n= bsp;            0x7000 0x0 0x0= 0x2 &ipic 18 0x8
          =        0x7000 0x0 0x0 0x3 &ipic 18 0x8
&nbs= p;               &nb= sp;0x7000 0x0 0x0 0x4 &ipic 18 0x8

     &nbs= p;          /* IDSEL 0x0F - PCI slot */<= br>              &nb= sp;  0x7800 0x0 0x0 0x1 &ipic 17 0x8
     &= nbsp;           0x7800 0x0 0x0 0x2 = &ipic 18 0x8
           = ;      0x7800 0x0 0x0 0x3 &ipic 17 0x8
 &nb= sp;               0x= 7800 0x0 0x0 0x4 &ipic 18 0x8>;
      &n= bsp; interrupt-parent =3D <&ipic>;
     &n= bsp;  interrupts =3D <66 0x8>;
      = ;  bus-range =3D <0x0 0x0>;
      &n= bsp; ranges =3D <0x02000000 0x0 0x90000000 0x90000000 0x0 0x10000000
=               0x42000000 = 0x0 0x80000000 0x80000000 0x0 0x10000000
      =         0x01000000 0x0 0x00000000 0xe2000000 0x0 0= x00100000>;
        clock-frequency =3D= <66666666>;
        #interrupt-cell= s =3D <1>;
        #size-cells =3D &= lt;2>;
        #address-cells =3D <3= >;
        reg =3D <0xe0008500 0x100= >;
        compatible =3D "fsl,mpc8349-= pci";
        device_type =3D "pci";
&n= bsp;   };
};


Ron


> Date: Tue, 6 May 2008 16:19:25 -0500
> From: scottwood@freesc= ale.com
> To: ron_madrid@hotmail.com
> CC: linuxppc-dev@ozlabs.= org
> Subject: Re: ifconfig MPC8313
>
> Ronald Madrid wr= ote:
> > Hello all,
> >
> > I am working on por= ting linux 2.6.25 with a custom MPC8313 based board,
> > but am h= aving a little bit of trouble with the ethernet, more
> > specifi= cally ifconfig.
> >
> > after typing "ifconfig eth0 10.1= 96.31.84" I receive the following error
> > ifconfig: SIOCSIFFLAGS= : Cannot assign requested address
> >
> > after entering= a MAC address via "ifconfig eth0 hw ether" I receive
> > this e= rror.
> > e0024520:01 not found
> > eth0: Could not attac= h to PHY
> > ifconfig: SIOCSIFFLAGS: No such device
>
&g= t; It can't find the PHY for eth0. What does your device tree look like, <= br>> and what is the relevant PHY address?
>
> -Scott

Windows Live SkyDrive lets you share files with faraway friends. = Start sharing. = --_05e3a848-ba53-45af-866c-d19a689830c5_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 2C26BDDF04 for ; Wed, 7 May 2008 07:34:50 +1000 (EST) Message-ID: <4820CF2A.5040301@freescale.com> Date: Tue, 06 May 2008 16:35:38 -0500 From: Scott Wood MIME-Version: 1.0 To: Ronald Madrid Subject: Re: ifconfig MPC8313 References: <4820CB5D.3000703@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ronald Madrid wrote: > I'm guessing by device tree you mean the .dts file? I'm using a > modified version of the mpc8313erdb.dts with minor changes (to the local > bus only). Here is a copy of it. OK, according to that device tree, eth0 is associated with PHY address 1. Is that correct on your board? -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc3-s37.bay0.hotmail.com (bay0-omc3-s37.bay0.hotmail.com [65.54.246.237]) by ozlabs.org (Postfix) with ESMTP id 29212DDE24 for ; Wed, 7 May 2008 07:41:56 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_2628b8f1-8fbc-43f8-b5b1-908ad0188450_" From: Ronald Madrid To: Scott Wood Subject: RE: ifconfig MPC8313 Date: Tue, 6 May 2008 14:41:55 -0700 In-Reply-To: <4820CF2A.5040301@freescale.com> References: <4820CB5D.3000703@freescale.com> <4820CF2A.5040301@freescale.com> MIME-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_2628b8f1-8fbc-43f8-b5b1-908ad0188450_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I don't know, where would I find that out? Sorry, I'm still kind of new to this. Ron > Date: Tue, 6 May 2008 16:35:38 -0500 > From: scottwood@freescale.com > To: ron_madrid@hotmail.com > CC: linuxppc-dev@ozlabs.org > Subject: Re: ifconfig MPC8313 >=20 > Ronald Madrid wrote: > > I'm guessing by device tree you mean the .dts file? I'm using a=20 > > modified version of the mpc8313erdb.dts with minor changes (to the loca= l=20 > > bus only). Here is a copy of it. >=20 > OK, according to that device tree, eth0 is associated with PHY address=20 > 1. Is that correct on your board? >=20 > -Scott _________________________________________________________________ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=3DTXT_TAGLM_WL_Refr= esh_messenger_052008= --_2628b8f1-8fbc-43f8-b5b1-908ad0188450_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I don't know, wh= ere would I find that out?

Sorry, I'm still kind of new to this.
=

Ron


> Date: Tue, 6 May 2008 16:= 35:38 -0500
> From: scottwood@freescale.com
> To: ron_madrid@ho= tmail.com
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig= MPC8313
>
> Ronald Madrid wrote:
> > I'm guessing by= device tree you mean the .dts file? I'm using a
> > modified ve= rsion of the mpc8313erdb.dts with minor changes (to the local
> >= bus only). Here is a copy of it.
>
> OK, according to that d= evice tree, eth0 is associated with PHY address
> 1. Is that correc= t on your board?
>
> -Scott


Stay in touch when = you're away with Windows Live Messenger. IM anytime you're online. = --_2628b8f1-8fbc-43f8-b5b1-908ad0188450_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id AFAC9DDEFE for ; Wed, 7 May 2008 07:43:10 +1000 (EST) Message-ID: <4820D11D.1050005@freescale.com> Date: Tue, 06 May 2008 16:43:57 -0500 From: Scott Wood MIME-Version: 1.0 To: Ronald Madrid Subject: Re: ifconfig MPC8313 References: <4820CB5D.3000703@freescale.com> <4820CF2A.5040301@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ronald Madrid wrote: > I don't know, where would I find that out? > > Sorry, I'm still kind of new to this. In the documentation/schematics/designer's-head of your custom board. -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc3-s15.bay0.hotmail.com (bay0-omc3-s15.bay0.hotmail.com [65.54.246.215]) by ozlabs.org (Postfix) with ESMTP id 97FCFDDE08 for ; Wed, 7 May 2008 07:56:45 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_f0b81097-1cca-4edb-bff3-bc8978fd1eec_" From: Ronald Madrid To: Scott Wood Subject: RE: ifconfig MPC8313 Date: Tue, 6 May 2008 14:56:44 -0700 In-Reply-To: <4820D11D.1050005@freescale.com> References: <4820CB5D.3000703@freescale.com> <4820CF2A.5040301@freescale.com> <4820D11D.1050005@freescale.com> MIME-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_f0b81097-1cca-4edb-bff3-bc8978fd1eec_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I believe that it is zero. Is that valid? Ron > Date: Tue, 6 May 2008 16:43:57 -0500 > From: scottwood@freescale.com > To: ron_madrid@hotmail.com > CC: linuxppc-dev@ozlabs.org > Subject: Re: ifconfig MPC8313 >=20 > Ronald Madrid wrote: > > I don't know, where would I find that out? > >=20 > > Sorry, I'm still kind of new to this. >=20 > In the documentation/schematics/designer's-head of your custom board. >=20 > -Scott _________________________________________________________________ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=3DTXT_TAGLM_WL_Refresh= _mobile_052008= --_f0b81097-1cca-4edb-bff3-bc8978fd1eec_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I believe that i= t is zero.  Is that valid?

Ron


> Date: Tue, 6 May 2008 16:43:57 -0500
> From: scottwood@free= scale.com
> To: ron_madrid@hotmail.com
> CC: linuxppc-dev@ozlab= s.org
> Subject: Re: ifconfig MPC8313
>
> Ronald Madrid = wrote:
> > I don't know, where would I find that out?
> >=
> > Sorry, I'm still kind of new to this.
>
> In th= e documentation/schematics/designer's-head of your custom board.
> > -Scott


With Windows Live for mobile, your contacts tr= avel with you. Connect on the go= . = --_f0b81097-1cca-4edb-bff3-bc8978fd1eec_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id B3D28DDF0B for ; Wed, 7 May 2008 08:03:33 +1000 (EST) Message-ID: <4820D5E5.9030509@freescale.com> Date: Tue, 06 May 2008 17:04:21 -0500 From: Scott Wood MIME-Version: 1.0 To: Ronald Madrid Subject: Re: ifconfig MPC8313 References: <4820CB5D.3000703@freescale.com> <4820CF2A.5040301@freescale.com> <4820D11D.1050005@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ronald Madrid wrote: > I believe that it is zero. Is that valid? FWIH, it's not recommended, as it's interpreted as a broadcast address in some cases. However, if that's the way the board is, then go ahead and put a zero in the phy node's reg property. -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc3-s33.bay0.hotmail.com (bay0-omc3-s33.bay0.hotmail.com [65.54.246.233]) by ozlabs.org (Postfix) with ESMTP id ED5EADDF00 for ; Wed, 7 May 2008 08:13:12 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_31bfbc24-f39f-432d-8cf5-0ed502a3e7a3_" From: Ronald Madrid To: Scott Wood Subject: RE: ifconfig MPC8313 Date: Tue, 6 May 2008 15:13:11 -0700 In-Reply-To: <4820D5E5.9030509@freescale.com> References: <4820CB5D.3000703@freescale.com> <4820CF2A.5040301@freescale.com> <4820D11D.1050005@freescale.com> <4820D5E5.9030509@freescale.com> MIME-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_31bfbc24-f39f-432d-8cf5-0ed502a3e7a3_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you, that seems to have worked. I can now ping and whatnot. One que= stion though. I used the linux v2.6.20 that came with the BSP for the MPC8= 313ERDB and the ethernet worked. Was there a bug earlier that would have a= llowed this default .dts to work with my phy address of '0'? I was rather = baffled with this problem as the two dts files seemed to be more or less fu= nctionally identical (2.6.20 from BSP vs. 2.6.25) Ron > Date: Tue, 6 May 2008 17:04:21 -0500 > From: scottwood@freescale.com > To: ron_madrid@hotmail.com > CC: linuxppc-dev@ozlabs.org > Subject: Re: ifconfig MPC8313 >=20 > Ronald Madrid wrote: > > I believe that it is zero. Is that valid? >=20 > FWIH, it's not recommended, as it's interpreted as a broadcast address=20 > in some cases. However, if that's the way the board is, then go ahead=20 > and put a zero in the phy node's reg property. >=20 > -Scott _________________________________________________________________ Make Windows Vista more reliable and secure with Windows Vista Service Pack= 1. http://www.windowsvista.com/SP1?WT.mc_id=3Dhotmailvistasp1banner= --_31bfbc24-f39f-432d-8cf5-0ed502a3e7a3_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thank you, that = seems to have worked.  I can now ping and whatnot.  One question = though.  I used the linux v2.6.20 that came with the BSP for the MPC83= 13ERDB and the ethernet worked.  Was there a bug earlier that would ha= ve allowed this default .dts to work with my phy address of '0'?  I wa= s rather baffled with this problem as the two dts files seemed to be more o= r less functionally identical (2.6.20 from BSP vs. 2.6.25)

Ron=


> Date: Tue, 6 May 2008 17:04:21 -0500> From: scottwood@freescale.com
> To: ron_madrid@hotmail.com
= > CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
&= gt;
> Ronald Madrid wrote:
> > I believe that it is zero. = Is that valid?
>
> FWIH, it's not recommended, as it's interpr= eted as a broadcast address
> in some cases. However, if that's the= way the board is, then go ahead
> and put a zero in the phy node's = reg property.
>
> -Scott


Make Windows Vista mor= e reliable and secure with Windows Vista Service Pack 1. = Learn more. = --_31bfbc24-f39f-432d-8cf5-0ed502a3e7a3_--