From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <greg@kroah.com>
Date: Sat, 02 Jul 2005 05:05:42 +0000
Subject: Re: sysdev_class use from DRM
Message-Id: <20050702050542.GC5303@kroah.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <9e473391050624071263dfbea7@mail.gmail.com>
In-Reply-To: <9e473391050624071263dfbea7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

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_id492&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