I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC Ethernet
controllers”, from the mpc85x0ads BSP.
Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
I would expect the driver to be able to auto negotiate the link speed
but only a Gigabit connection to the card works, if I try with 100Mbit
ping or telnet failed. I can connect with 100Mbit only if I specify the
option speed=100.
Any suggestion.
The ethernet phy is a Marvell 88E1111 and it always indicates the right
connection speed (1Gbit or 100Mbit).
Are you using this with an 85x0ADS board or with custom hardware? Do
you have a source code entitlement to the driver or binary only?
Robert.
Armand Ciejak wrote:
I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC Ethernet
controllers”, from the mpc85x0ads BSP.
Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
I would expect the driver to be able to auto negotiate the link speed
but only a Gigabit connection to the card works, if I try with 100Mbit
ping or telnet failed. I can connect with 100Mbit only if I specify the
option speed=100.
Any suggestion.
The ethernet phy is a Marvell 88E1111 and it always indicates the right
connection speed (1Gbit or 100Mbit).
Hi Armand:
Lots of questions here 
. What does “sloginfo” tell you as you
switch from GigE to 100? What does “nicinfo” give you? Does the phy
address for the interface match the phy address on the PHY?
R.
Armand Ciejak wrote:
I use a custom hardware, which is similar (but obviously not the same as
the 85x0ADS board). Yes I have the source code of the driver.
Armand
Robert Craig wrote:
Are you using this with an 85x0ADS board or with custom hardware? Do
you have a source code entitlement to the driver or binary only?
Robert.
Armand Ciejak wrote:
I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC
Ethernet controllers”, from the mpc85x0ads BSP.
Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
I would expect the driver to be able to auto negotiate the link speed
but only a Gigabit connection to the card works, if I try with
100Mbit ping or telnet failed. I can connect with 100Mbit only if I
specify the option speed=100.
Any suggestion.
The ethernet phy is a Marvell 88E1111 and it always indicates the
right connection speed (1Gbit or 100Mbit).
The problem was that the driver expect PHYs to be at address 0 and 1 and our board is configured
with address 7 and 4. I tweaked the driver so that it handles our configuration and now everything
works fine.
Armand
Robert Craig wrote:
Hi Armand:
Lots of questions here > > . What does “sloginfo” tell you as you
switch from GigE to 100? What does “nicinfo” give you? Does the phy
address for the interface match the phy address on the PHY?
R.
Armand Ciejak wrote:
I use a custom hardware, which is similar (but obviously not the same
as the 85x0ADS board). Yes I have the source code of the driver.
Armand
Robert Craig wrote:
Are you using this with an 85x0ADS board or with custom hardware? Do
you have a source code entitlement to the driver or binary only?
Robert.
Armand Ciejak wrote:
I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC
Ethernet controllers”, from the mpc85x0ads BSP.
Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
I would expect the driver to be able to auto negotiate the link
speed but only a Gigabit connection to the card works, if I try with
100Mbit ping or telnet failed. I can connect with 100Mbit only if I
specify the option speed=100.
Any suggestion.
The ethernet phy is a Marvell 88E1111 and it always indicates the
right connection speed (1Gbit or 100Mbit).