On Tue, 21 Jan 2003, Adam Belay wrote:
> How does this sound...
> 1.) detach pnp card service matching from the driver model, the driver model is
> what is imposing this one card per driver limit.
> 2.) create a special pnp_driver that handles cards and forwards driver model calls
> to the pnp card services, we can use attach_driver to avoid matching problems.
> design goals for these changes should be as follows:
> 1.) multiple drivers can bind to one card
> 2.) pnp_attach, pnp_detach, and pnp status should be phased out and replaced with
> the special card driver, in other words the driver model can take care of this.
First of all I admit that I haven't been following closely, so I maybe way
Anyway, the old ISAPnP used, AFAIR, struct pci_bus for the card and struct
pci_device for the devices. So what's wrong with using the basically the
same abstraction with the driver model, which has buses and devices as
well. That means each device can have its own driver, and I suppose that
should be good enough (as opposed to only one driver per card).
But probably I'm missing something?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 23 2003 - 22:00:28 EST