Am Dienstag, 4. Juni 2002 20:54 schrieben Sie:
> On Tue, Jun 04, 2002 at 11:28:48AM -0700, David Brownell wrote:
> > Greg KH wrote:
> > >FWIW, Pat Mochel has just posted some documentation on the new kernel
> > >driver model code to linux-kernel if people are interested in seeing how
> > >it will effect the USB core.
> >
> > In three parts, no less ... :)
> >
> >   http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912115&w=2
> >   http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912113&w=2
> >   http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912119&w=2
> >
> > To land in Documentation/* sometime soonish, so I guess feedback
> > now would be handy!
>
> Yes it would.

I am still mentally digesting.

> > As for how it affects the USB code ... I thought the goal was to
> > have that be more or less invisible, except within the core or for
> > anything manipulating the device tree.
>
> That was the goal, but the init api looks like it will change a bit (two
> stage, probe / init) and probably all drivers will have to change to
> support the new structure.  Most of the work is still in the USB core,
> moving lots of the device handling logic into the generic driver code.

Would that not be the place to check vendor/product id in core
and make a call into the drivers optional ?

Does an error in init() mean that the system will give up on the device ?

        Regards
                Oliver

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to