From: David Miller <davem@davemloft•net>
To: broonie@opensource•wolfsonmicro.com
Cc: mfuzzey@gmail•com, bhutchings@solarflare•com, nico@cam•org,
netdev@vger•kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver configuration.
Date: Fri, 12 Jun 2009 04:33:50 -0700 (PDT) [thread overview]
Message-ID: <20090612.043350.38954875.davem@davemloft.net> (raw)
In-Reply-To: <20090612105019.GA21599@sirena.org.uk>
From: Mark Brown <broonie@opensource•wolfsonmicro.com>
Date: Fri, 12 Jun 2009 11:50:20 +0100
> 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.
It's irrelevant in this discussion because in the contexts where
this is wanted, people are adding driver-wide hacks to make
these settings.
So a dummy platform_device would serve handily.
For PCI, in general, the VPD or openfirmware descriptions could
be used to describe such issues.
next prev parent reply other threads:[~2009-06-12 11:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:34 [RFC PATCH] Ethtool style in kernel network driver configuration Martin Fuzzey
2009-06-10 18:02 ` Joe Perches
2009-06-11 2:02 ` Ben Hutchings
2009-06-11 3:55 ` Nicolas Pitre
2009-06-11 6:47 ` Martin Fuzzey
2009-06-11 14:54 ` Ben Hutchings
2009-06-11 16:22 ` Nicolas Pitre
2009-06-11 16:52 ` Ben Hutchings
2009-06-11 17:44 ` Nicolas Pitre
2009-06-11 18:29 ` Ben Hutchings
2009-06-11 19:08 ` Nicolas Pitre
2009-06-11 19:31 ` Ben Hutchings
2009-06-11 20:24 ` Nicolas Pitre
2009-06-11 20:48 ` Ben Hutchings
2009-06-11 21:39 ` Martin Fuzzey
2009-06-12 0:15 ` David Miller
2009-06-12 0:38 ` Nicolas Pitre
2009-06-12 2:57 ` David Miller
2009-06-11 17:45 ` Martin Fuzzey
2009-06-12 0:09 ` David Miller
2009-06-12 10:50 ` Mark Brown
2009-06-12 11:33 ` David Miller [this message]
2009-06-12 12:24 ` Mark Brown
2009-06-13 0:01 ` David Miller
2009-06-13 17:10 ` Mark Brown
2009-06-12 12:19 ` Martin Fuzzey
2009-06-13 0:01 ` David Miller
2009-06-13 7:00 ` Martin Fuzzey
2009-06-13 7:07 ` David Miller
2009-06-13 7:51 ` Martin Fuzzey
2009-06-13 8:07 ` David Miller
2009-06-13 9:29 ` Martin Fuzzey
2009-06-14 18:39 ` Martin Fuzzey
2009-06-12 0:07 ` David Miller
2009-06-12 0:03 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090612.043350.38954875.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=bhutchings@solarflare$(echo .)com \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=mfuzzey@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nico@cam$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox