netdev
[Top] [All Lists]

Re: Options for forcedeth Linux kernel module

To: Andreas Sindermann <sinder@xxxxxxxxxxxxxxxx>
Subject: Re: Options for forcedeth Linux kernel module
From: Francois Romieu <romieu@xxxxxxxxxxxxx>
Date: Sun, 14 Nov 2004 12:53:00 +0100
Cc: Michal Schmidt <xschmi00@xxxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, c-d.hailfinger.kernel.2004@xxxxxxx, manfred@xxxxxxxxxxxxxxxx
In-reply-to: <200411141028.iAEASVL27021@xxxxxxxxxxxxxxxxxxxxxx>
References: <200411131913.iADJDZ321996@xxxxxxxxxxxxxxxxxxxxxx> <41971E3B.40605@xxxxxxxxxxxxxxxxxx> <200411141028.iAEASVL27021@xxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
Andreas Sindermann <sinder@xxxxxxxxxxxxxxxx> :
[...]
> Thanks for your answer! I tried ethtool but without success. The
> mii-tool doesn't seem to be delivered with Suse 9.2 and I can't find
> the sources right now on the net. Here what I tried with ethtool:
> 
> linux3:~ # ethtool  -s eth0 speed 100 duplex full autoneg off
> Cannot get current device settings: Operation not supported
>   not setting speed
>   not setting duplex
>   not setting autoneg
[...]
> So unfortunately ethtool doesn't seem to work properly for me at the
> moment.

At least in 2.6.10-rc1-bk20 + 2.6.10-rc1-bk14-netdev1, the driver does
not provide a set_settings() method in its ethtool_ops structure. It
does not use generic_mii_ioctl() or support SIOC#MII### either.
So neither ethtool nor mii-tool will allow you to set the required
option.

Otoh it seems that phy_init() contains most of the code one needs to
glue to have mii-tool/ethtool support.

--
Ueimor

<Prev in Thread] Current Thread [Next in Thread>