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: <20090611.170948.66762524.davem@davemloft.net>
Date:	Thu, 11 Jun 2009 17:09:48 -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: Thu, 11 Jun 2009 19:45:07 +0200

> The problems with the quick hack approach are:
> 1) Different for each driver
> 2) Need to understand how each driver works to do it
> 3) Need to maintain the driver patch against evolving kernel

Hardware specific solutions for hardware specific problems.

You can instantiate a platform_device that the driver matches
and uses to acquire board-specific-juju such as link modes
which are non-functional.
--
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