From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: sysdev_class use from DRM
Date: Sat, 02 Jul 2005 05:05:42 +0000 [thread overview]
Message-ID: <20050702050542.GC5303@kroah.com> (raw)
In-Reply-To: <9e473391050624071263dfbea7@mail.gmail.com>
On Fri, Jul 01, 2005 at 07:18:08PM -0400, Jon Smirl wrote:
> On 7/1/05, Greg KH <greg@kroah.com> wrote:
> > Last kernel summit I thought this was all hashed out. I guess the
> > people not there didn't agree...
>
> There are more layers to the problem.
{sigh} there always is...
<good reasons snipped>
What about starting small, with just the pci driver functions, and going
on from there. That way you all can still fight it out over the
different details, and I'll be happy that you play nice with the driver
core. Something as simple as:
register_my_driver(struct pci_driver *drv)
{
/* add drv to list of drivers that want to use this hardware */
}
struct pci_driver foo = {
.owner = THIS_MODULE,
.name = "foo_video_multiplexor",
.id_table = all_foo_ids_combined,
.probe = foo_probe,
.suspend = foo_suspend,
...
};
static int foo_probe(struct pci_dev *dev, id)
{
for (all drivers registered with me)
drv->probe(dev, id);
}
and so on...
That would be a good start...
> > Hey, how about at KS/OLS we (anyone who cares about this) sit down and
> > hash it all out and produce code that does this? With a working patch,
> > it should be simple to get it into the tree and then everyone can move
> > on.
>
> I am still uncommitted to coming. We have a new set of eight month old
> twins
Say no more. I totally understand, don't worry about it, not a big
deal.
> and I can't get permission to leave.
If I was your wife, I wouldn't give you permission either :)
> This is not an easy area to get consensus on. You can get agreements
> from small groups but when it expands the agreements fall apart. It
> may require that someone like Linus bless a roadmap for video
> development and then reject anything that is not on the roadmap.
I thought we almost had that last year. Did I miss something?
> With road we are on right now we are going to end up with ten
> different half finished systems.
Which I really don't want to see.
Want me to write up the above in real code for you all to use? Anything
else I can do to help fix this? Anyone you want me to confront at OLS
and "persuade"?
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-07-02 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 14:12 sysdev_class use from DRM Jon Smirl
2005-06-24 19:21 ` Jon Smirl
2005-06-24 21:08 ` Dmitry Torokhov
2005-06-30 17:40 ` Greg KH
2005-06-30 20:55 ` Jon Smirl
2005-07-01 22:23 ` Greg KH
2005-07-01 23:18 ` Jon Smirl
2005-07-02 5:05 ` Greg KH [this message]
2005-07-02 13:34 ` Jon Smirl
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=20050702050542.GC5303@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).