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: <20090612122431.GA8861@rakim.wolfsonmicro.main>
Date:	Fri, 12 Jun 2009 13:24:32 +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 Fri, Jun 12, 2009 at 04:33:50AM -0700, David Miller wrote:
> From: Mark Brown <broonie@...nsource.wolfsonmicro.com>

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

> It's irrelevant in this discussion because in the contexts where
> this is wanted, people are adding driver-wide hacks to make
> these settings.

...which work well enough locally have problems getting upstream.

> For PCI, in general, the VPD or openfirmware descriptions could
> be used to describe such issues.

Where this is needed for PCI devices the VPD isn't useful - the hardware
often won't have the SEPROM (or whatever) that the device is intended to
load configuration from for cost or production reasons, the data being
provided elsewhere through something like OpenFirmware.

OpenFirmware works well enough on the platforms that use it but it's far
from universal.
--
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