eth0 autonegotation 8260

eth0 autonegotation 8260

[Samuel Osorio Calvo]

Hi!

First of all sorry if this answer has been answered before, I have looked =
into the archives and did not find the answer.

We are using a 8260 processor with ELDK 3.1.1,  kernel 2.4.25 patched with =
lck1. We have configured the kernel with USE_MDIO and LXT971.
The problem we face is that the boot process stops after displaying the =
configuration of the card:
eth0: config: autonegotiation on, 100FDX,...
and after the board seems to freeze.

Following the code, I located the error in the startup command of the =
LXT971, concretely in the line setting the autonegotiation:
{mk_mii_write(MII_REG_CR, 0x1200), NULL}, /* autonegotiate */=20

Can anybody provide some feedback on how to check what can be misconfigured=
 or where to look for the error???=20

Thanks in advance,

Samuel.



Unclassified.

Re: eth0 autonegotation 8260

[Mark Chambers]

>We are using a 8260 processor with ELDK 3.1.1,  kernel 2.4.25 patched with
lck1. We have configured the kernel with USE_MDIO >and LXT971.
>The problem we face is that the boot process stops after displaying the
configuration of the card:
>eth0: config: autonegotiation on, 100FDX,...
>and after the board seems to freeze.
>
>Can anybody provide some feedback on how to check what can be misconfigured
or where to look for the error???

Check that the interrupt from the LXT971 is configured correctly.
The code is probably waiting for this interrupt to tell it that negotiation
is complete

Mark Chambers

Re: eth0 autonegotation 8260

[Alex Zeffertt]

> >We are using a 8260 processor with ELDK 3.1.1,  kernel 2.4.25 patched with
> >lck1. We have configured the kernel with USE_MDIO 
> >and LXT971.
> >The problem we face is that the boot process stops after displaying the
> >configuration of the card:
> >eth0: config: autonegotiation on, 100FDX,...
> >and after the board seems to freeze.
> >
> >Can anybody provide some feedback on how to check what can be misconfigured
> >or where to look for the error???
> 
> Check that the interrupt from the LXT971 is configured correctly.
> The code is probably waiting for this interrupt to tell it that negotiation
> is complete
> 

On a similar note... I've noticed that the fcc_enet driver does not appear to
detect when the link goes down, or re-autonegotiate when it comes back up.  I
wonder if anybody has a fix for this?

PS I too am using the ELDK 3.1.1 linux-2.4.25 kernel, but with a PM828 devel
board.

Re: eth0 autonegotation 8260

[Alex Zeffertt]

> 
> On a similar note... I've noticed that the fcc_enet driver does not appear to
> detect when the link goes down, or re-autonegotiate when it comes back up.  I
> wonder if anybody has a fix for this?
> 
> PS I too am using the ELDK 3.1.1 linux-2.4.25 kernel, but with a PM828 devel
> board.

Sorry all, I think I've spotted the problem now.  From fcc_enet.c:

	/* Some boards don't have the MDIRQ line connected (PM826 is such a board) */

Alex

Re: eth0 autonegotation 8260

[aris]

> First of all sorry if this answer has been answered before, I have looked into the archives and did not find the answer.
> 
> We are using a 8260 processor with ELDK 3.1.1,  kernel 2.4.25 patched with lck1. We have configured the kernel with USE_MDIO and LXT971.
> The problem we face is that the boot process stops after displaying the configuration of the card:
> eth0: config: autonegotiation on, 100FDX,...
> and after the board seems to freeze.
> 
> Following the code, I located the error in the startup command of the LXT971, concretely in the line setting the autonegotiation:
> {mk_mii_write(MII_REG_CR, 0x1200), NULL}, /* autonegotiate */ 
I have the same here but it doesn't freezes, it just doesn't works :).
(maybe it "freezes" because next step depends on the eth like RARP?)
I digged into LXT971 datasheet and 0x1200 appears to be correct. I was thinking
in add an module option to manually set it (and thus avoiding the need to use
ethtool). Any MII guru around to help us on this?

--
Aristeu

Re: eth0 autonegotation 8260

[Samuel Osorio Calvo]

First of all , thanks to all who replied,

It is definetely related to interrupts since starting the target without =
the eth wire plugged enables me to login into the board. Of course, =
without network connectivity......and whenever the wire is connected ->the =
board freezes again (no message, no panic, nothing....).

The boot process seems everything ok,  the request_irq returns ok for both =
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 =
clocks and MDIO pins. I took changes somebody made with DENX's 2.4.18 and =
ported them to 2.4.25, probably forgeting something in the way....may be =
something related to interrupts interfaces has changed since then???=20


Any feedback will be higly wellcome,

Samuel.


Unclassified.
>>> "Mark Chambers" <markc@mail.com> 06/30/05 04:04PM >>>
>We are using a 8260 processor with ELDK 3.1.1,  kernel 2.4.25 patched =
with
lck1. We have configured the kernel with USE_MDIO >and LXT971.
>The problem we face is that the boot process stops after displaying the
configuration of the card:
>eth0: config: autonegotiation on, 100FDX,...
>and after the board seems to freeze.
>
>Can anybody provide some feedback on how to check what can be misconfigure=
d
or where to look for the error???

Check that the interrupt from the LXT971 is configured correctly.
The code is probably waiting for this interrupt to tell it that negotiation=

is complete

Mark Chambers

Re: eth0 autonegotation 8260

[Ricardo Scop]

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/)

Re: eth0 autonegotation 8260

[Wolfgang Denk]

Dear Samuel,

in message <s2c4339f.015@scms1.sc.signaal.nl> you wrote:
> 
...
> clocks and MDIO pins. I took changes somebody made with DENX's 2.4.18 and
> ported them to 2.4.25, probably forgeting something in the way....may be
> something related to interrupts interfaces has changed since then??? 

Ummm.... did you by chance try the  currnt  code  in  CVS,  which  is
2.4.25  based?  I am not aware of any problems in that area, at least
not on the boards we use for regular testing.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Anyone who isn't confused here doesn't really know what's going on.