Date: Mon, 21 Mar 2005 23:30:36 +0200 (IST)
From: Jacques Goldberg <goldberg@phep2.technion.ac.il>
Reply-To: Jacques Goldberg <Jacques.Goldberg@cern.ch>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Need break driver<-->pci-device automatic association
In-Reply-To: <20050321210948.B17493@flint.arm.linux.org.uk>
Message-ID: <Pine.LNX.4.58_heb2.09.0503212326040.8166@localhost.localdomain>
References: <Pine.LNX.4.58_heb2.09.0503181042470.8660@localhost.localdomain>
 <20050318165124.GC14952@kroah.com> <Pine.LNX.4.58_heb2.09.0503192021431.11358@localhost.localdomain>
 <20050321081638.GC2703@pazke> <20050321082228.A22099@flint.arm.linux.org.uk>
 <Pine.LNX.4.58_heb2.09.0503211336090.6491@localhost.localdomain>
 <20050321201847.A16069@flint.arm.linux.org.uk>
 <Pine.LNX.4.58_heb2.09.0503212248010.7910@localhost.localdomain>
 <20050321210948.B17493@flint.arm.linux.org.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 877
Lines: 22


On Mon, 21 Mar 2005, Russell King wrote:

> What it comes back to is that we _need_ driver match priorities, so we
> can detect when a more specific driver for the device is loaded (iow
> one which matches by vendor+device rather than just class), unbind the
> existing driver, and bind the more specific one.

  Absolutely agreed. This is what I dreamt of when starting this thread.
  My job is done now. The ball is in your hands.
  I shall now become mute but shall read further.
  If you ever need a real test you will always be welcome  to send it to
me since I have a case hardware.

  Thanks to all of you. Cheers. Jacques
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/