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: <20090612105019.GA21599@sirena.org.uk>
Date:	Fri, 12 Jun 2009 11:50:20 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	David Miller <davem@...emloft.net>
Cc:	mfuzzey@...il.com, bhutchings@...arflare.com, nico@....org,
	netdev@...r.kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver
	configuration.

On Thu, Jun 11, 2009 at 05:09:48PM -0700, David Miller wrote:

> 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.

How would you handle PCI devices in that scheme?  Last time I looked at
this (a while ago, so I may be out of date) there didn't appear to be a
sensible generic way of getting platform data to PCI devices.
--
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