linux-kernel - Re: [patch 2.6.21-rc5-git 1/2] fix hotplug for legacy platform drivers

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 2 Apr 2007 16:10:17 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"David Brownell" <david-b@...bell.net>
Cc:	"Greg KH" <gregkh@...e.de>,
	"Linux Kernel list" <linux-kernel@...r.kernel.org>,
	"Andres Salomon" <dilinger@...ian.org>
Subject: Re: [patch 2.6.21-rc5-git 1/2] fix hotplug for legacy platform drivers

On 3/31/07, David Brownell <david-b@...bell.net> wrote:
> @@ -349,6 +360,13 @@ EXPORT_SYMBOL_GPL(platform_device_unregi
>  *     memory allocated for the device allows drivers using such devices
>  *     to be unloaded iwithout waiting for the last reference to the device
>  *     to be dropped.
> + *
> + *     This interface is primarily intended for use with legacy drivers
> + *     which probe hardware directly.  Because such drivers create device
> + *     nodes themselves, rather than letting system infrastructure handle
> + *     such device enumeration tasks, they don't fully conform to the Linux
> + *     driver model.  In particular, when such drivers are built as modules,
> + *     they can't be "hotplugged".
>  */
>  struct platform_device *platform_device_register_simple(char *name, unsigned int id,

I find this comment misleading. Many of these drivers do not create
any devices (as in /dev/xxx) but rather create underlying hardware
abstraction objects.


-- 
Dmitry
-
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/