linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "robert lazarski" <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 85xx Device tree problems: e0024520:02 not found
Date: Wed, 14 Nov 2007 17:00:49 -0500	[thread overview]
Message-ID: <f87675ee0711141400u5de89f17jc7934f8690a9fac9@mail.gmail.com> (raw)
In-Reply-To: <473B699C.5040700@anagramm.de>

On Nov 14, 2007 4:33 PM, Clemens Koller <clemens.koller@anagramm.de> wrote:
> Hi, Robert!
>
> Just one more short note...
> My good - vs. - bad dmesg output:
>
> good 2.6.21-rc5-git:
>  > Gianfar MII Bus: probed
>  > eth0: Gianfar Ethernet Controller Version 1.2, 00:ww:xx:yy:zz:dd
>  > eth0: Running with NAPI enabled
>  > eth0: 256/256 RX/TX BD ring size
>  > eth1: Gianfar Ethernet Controller Version 1.2, 00:ww:xx:yy:zz:dd
>  > eth1: Running with NAPI enabled
>  > eth1: 256/256 RX/TX BD ring size
>  > eth2: Gianfar Ethernet Controller Version 1.2, 00:ww:xx:yy:zz:dd
>  > eth2: Running with NAPI enabled
>  > eth2: 256/256 RX/TX BD ring size
>  > Marvell 88E1101: Registered new driver
>  > Marvell 88E1111: Registered new driver
>  > Marvell 88E1145: Registered new driver
> (I've wiped out my MAC)
>
> bad 2.6.24-rc2-git:
> < Gianfar MII Bus: probed
> < eth0: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:00:00
> < eth0: Running with NAPI enabled
> < eth0: 256/256 RX/TX BD ring size
> < eth1: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:00:00
> < eth1: Running with NAPI enabled
> < eth1: 256/256 RX/TX BD ring size
> < eth2: Gianfar Ethernet Controller Version 1.2, 00:00:00:00:00:00
> < eth2: Running with NAPI enabled
> < eth2: 256/256 RX/TX BD ring size
>
> The MACs are all 00 here.
> The PHY drivers don't get registered.
> (What happened to CONFIG_NETDEV_1000 in the newer kernels?)
>
> How is your mileage?
> Next round... tomorrow,
>
> regards,
>
> Clemens Koller

Hmm, I'm getting my mac addresses, the same ones I set in u-boot:

=> bootm 1000000 - c00000
## Booting image at 01000000 ...
   Image Name:   Linux-2.6.24-rc2-ge6a5c27f-dirty
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1278631 Bytes =  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x3FF9DD50 => set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF90
bd address  = 0x3FF9DFB0
memstart    = 0x00000000
memsize     = 0x40000000
flashstart  = 0xF8000000
flashsize   = 0x08000000
flashoffset = 0x00000000
sramstart   = 0x00000000
sramsize    = 0x00000000
immr_base   = 0xE0000000
bootflags   = 0xE4013F80
intfreq     = 888.888 MHz
busfreq     = 355.555 MHz
ethaddr     = 00:E0:0C:00:00:FD
eth1addr    = 00:E0:0C:00:01:FD
eth2addr    = 00:E0:0C:00:02:FD
eth3addr    = 00:E0:0C:00:03:FD
IP addr     = 10.101.43.142
baudrate    = 115200 bps
Skipping initrd
   Booting using the fdt at 0xc00000
No initrd
## device tree at 0x00C00000 ... 0x00C01B6C (len=7021=0x1B6D)
   Loading Device Tree to 007fc000, end 007fdb6c ... OK
## Transferring control to Linux (at address 00000000) ...
serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 42) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: module loaded
Gianfar MII Bus: probed
eth0: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:00:fd
eth0: Running with NAPI enabled
eth0: 256/256 RX/TX BD ring size
eth1: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:01:fd
eth1: Running with NAPI enabled
eth1: 256/256 RX/TX BD ring size
eth2: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:02:fd
eth2: Running with NAPI enabled
eth2: 256/256 RX/TX BD ring size
eth3: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:03:fd
eth3: Running with NAPI enabled
eth3: 256/256 RX/TX BD ring size
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
e0024520:02 not found
eth2: Could not attach to PHY
IP-Config: Failed to open eth2
IP-Config: Device `eth2' not found.

Tomorrow's a holiday here in Brazil, will catch up with you Friday,
Robert

      reply	other threads:[~2007-11-14 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 20:17 85xx Device tree problems: e0024520:02 not found robert lazarski
2007-11-13 20:33 ` Clemens Koller
2007-11-14 19:18   ` robert lazarski
2007-11-14 19:37     ` Clemens Koller
2007-11-14 20:23     ` Clemens Koller
2007-11-14 21:33       ` Clemens Koller
2007-11-14 22:00         ` robert lazarski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f87675ee0711141400u5de89f17jc7934f8690a9fac9@mail.gmail.com \
    --to=robertlazarski@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).