linux-kernel - Re: about probing a device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Oct 2007 21:46:19 -0700
From:	Greg KH <greg@...ah.com>
To:	wit <is01kzh@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: about probing a device

On Wed, Oct 10, 2007 at 09:39:44AM +0800, wit wrote:
> Hi,
> I found these routines in the kernel, does this means only one driver
> can be matched to a device?

Yes, you are correct, that is how the driver model currently works.

> What if two drivers both can drive the device, like sd & sg in scsi
> subsystem?

You have to go through a lot of pain to get it to work :)

Or create a virtual bus and devices, but that is not how scsi decided to
go about this.

I do have some half-baked patches to fix this in a generic way, to allow
multiple drivers to bind to devices, but it's not fully working right
now and I got side-tracked by having to clean up the kset/kobject/ktype
mess first to get this to work properly, so it might be a few months.

Why, is there some use for multiple drivers to devices that you want to
use?

thanks,

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