From: Ricardo Scop <rscop@matrix•com.br>
To: "Samuel Osorio Calvo" <samuel.osorio@nl•thalesgroup.com>,
<markc@mail•com>, <linuxppc-embedded@ozlabs•org>
Subject: Re: eth0 autonegotation 8260
Date: Thu, 30 Jun 2005 20:15:53 -0300 [thread overview]
Message-ID: <200506302015.53594.rscop@matrix.com.br> (raw)
In-Reply-To: <s2c4339f.015@scms1.sc.signaal.nl>
Hi, Samuel
On Thursday 30 June 2005 13:01, Samuel Osorio Calvo wrote:
> First of all , thanks to all who replied,
>
> It is definetely related to interrupts since starting the target withou=
t
> the eth wire plugged enables me to login into the board. Of course, wit=
hout
> network connectivity......and whenever the wire is connected ->the boar=
d
> freezes again (no message, no panic, nothing....).
Well, some fcc-related interrupt is problably ocurring, then. You should=20
attach a BDI2000 to continue debugging, or at least put some printk in=20
fcc_enet code to see which interrupts are ocurring and what happens then.
>
> The boot process seems everything ok, the request_irq returns ok for b=
oth
> the mii and the fcc. I am not using a commercial board and some tuning =
were
> made to the kernel to adjust to the hardware configuration, mainly cloc=
ks
> and MDIO pins. I took changes somebody made with DENX's 2.4.18 and port=
ed
> them to 2.4.25, probably forgeting something in the way....may be somet=
hing
> related to interrupts interfaces has changed since then???
Yes, many things may have happened, but we don't know what because we don=
't=20
have your ported code...
HTH,
-Scop.
=2Eo.
=2E.o
ooo (http://www.catb.org/hacker-emblem/)
next prev parent reply other threads:[~2005-06-30 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 16:01 eth0 autonegotation 8260 Samuel Osorio Calvo
2005-06-30 23:15 ` Ricardo Scop [this message]
2005-06-30 23:54 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 13:52 Samuel Osorio Calvo
2005-06-30 14:04 ` Mark Chambers
2005-06-30 14:32 ` Alex Zeffertt
2005-06-30 15:06 ` Alex Zeffertt
2005-06-30 14:11 ` aris
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=200506302015.53594.rscop@matrix.com.br \
--to=rscop@matrix$(echo .)com.br \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=markc@mail$(echo .)com \
--cc=samuel.osorio@nl$(echo .)thalesgroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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