linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug arch. and apps
Date: Fri, 16 Nov 2001 04:06:48 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100588356117815@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100585666514602@msgid-missing>

My original devfs based patch used a priority number. Basically the the
biggest priority got elected to be the driver to be loaded and bound to
the interface.

It was arbitrary and less than perfect.

The only thing I can think of now is to favor vendor specific alternate
settings over class alternate settings. I'm not sure if this is the best
assumption to make however.

JE

On Thu, Nov 15, 2001, David Brownell <david-b@pacbell.net> wrote:
> Johannes, what sort of policy criteria would you suggest for
> choosing one driver versus another?
> 
> The "usbmodules" command is able to use richer inputs to
> its policy.  Right now what it does is exactly mimic the policy
> that the kernel uses.
> 
> Seems we'd need to start recording (preferably in the kernel
> and then exported) things like "prefer uss720 to printer".
> 
> So far my thought in this area has been that the kernel
> needs to stay simple, and this sort of logic can be done
> in userland given suitable binding/unbinding/rebinding
> hooks in the kernel.
> 
> - Dave
> 
> 
> ----- Original Message ----- 
> From: "Johannes Erdfelt" <johannes@erdfelt.com>
> To: "Greg KH" <greg@kroah.com>
> Cc: <linux-hotplug-devel@lists.sourceforge.net>
> Sent: Thursday, November 15, 2001 5:42 PM
> Subject: Re: hotplug arch. and apps
> 
> 
> > On Thu, Nov 15, 2001, Greg KH <greg@kroah.com> wrote:
> > > On Thu, Nov 15, 2001 at 03:39:58PM -0800, Scott Cuyle Fritzinger wrote:
> > > > yup! from what i've read, it seems like the modules.usbmap has 'first
> > > > dibs' on any device, and then the usb.handmap is referenced if nothing
> > > > matches there.
> > > 
> > > Exactly.
> > 
> > This is something I'd like to fix at some point. We haven't solved the
> > problem of devices with multiple alternate settings that can be handled
> > by multiple drivers.
> > 
> > Like the uss720 chips which have a native mode and a USB printer class
> > alternate setting.
> > 
> > We should prefer to use the native mode in that case.
> > 
> > JE
> > 
> > 
> 
> 

_______________________________________________
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

  parent reply	other threads:[~2001-11-16  4:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 20:38 hotplug arch. and apps Scott Cuyle Fritzinger
2001-11-15 20:48 ` Stephen Williams
2001-11-15 21:45 ` Scott Cuyle Fritzinger
2001-11-15 21:51 ` Stephen Williams
2001-11-15 22:02 ` Greg KH
2001-11-15 22:51 ` David Brownell
2001-11-15 23:39 ` Scott Cuyle Fritzinger
2001-11-15 23:44 ` Scott Cuyle Fritzinger
2001-11-16  1:42 ` Johannes Erdfelt
2001-11-16  2:26 ` Greg KH
2001-11-16  3:42 ` David Brownell
2001-11-16  4:06 ` Johannes Erdfelt [this message]
2001-11-16 16:11 ` Ken Hahn
2001-11-16 19:45 ` Scott Cuyle Fritzinger

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=marc-linux-hotplug-100588356117815@msgid-missing \
    --to=johannes@erdfelt.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).