netdev - Re: SMC91x: forcing speed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Jun 2009 14:02:05 +0200
From:	Martin Fuzzey <mfuzzey@...il.com>
To:	Richard Röjfors <richard.rojfors@...ian.se>
Cc:	nico@....org, netdev@...r.kernel.org
Subject: Re: SMC91x: forcing speed

> Martin Fuzzey wrote:
>> Hi,
>>
>> Is there a better way of doing this that would be acceptable for mainline?
>
> Look at include/linux/ethtool.h.
>

Thank you for your reply.

The smc91x driver already has ethtool support.
However, as I stated in my original post, I don't want to use ethtool
from userspace since I need to be able to use a NFS rootfs.

So is there already a programmatic way of using the ethool interface
from the board specific setup code?
Or are you proposing adding a struct ethtool_cmd to smc91x_platdata ?

Another way I can think of is just to add a generic init() callback to
the platform data so that my board specific code can get at the
struct net_device * and then use the ethtool interface via dev->ethtool_ops.

Regards,

Martin
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html