netdev - Re: [RFC PATCH] Ethtool style in kernel network driver configuration.

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]

Message-Id: <20090613.000729.118500646.davem@davemloft.net>
Date:	Sat, 13 Jun 2009 00:07:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mfuzzey@...il.com
Cc:	bhutchings@...arflare.com, nico@....org, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver
 configuration.

From: Martin Fuzzey <mfuzzey@...il.com>
Date: Sat, 13 Jun 2009 09:00:10 +0200

> But please reply to the rest of that message, in particular explain why,
> having publicly stated you would accept an implementation of Nicolas'
> idea, you are now back pedaling.

I misunderstood the problem, thanks for asking me to clarify
this.

I thought the issue was the "in the environment where his devices
would be used" he wanted to force a certain link speed and duplex
setting.  In that case, forcing the link via ethtool is appropriate
because it's an attribute of where the device is connected.

But the situation is different, the physical hardware has a limitation
and know of this belongs, or should be described, in the driver
somehow.
--
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