linux-kernel - Re: Creating dev nodes from driver or via uevent?

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]

Message-ID: <df9815e70810150023w2a14fad5ge08ea4edad4ae0b1@mail.gmail.com>
Date:	Wed, 15 Oct 2008 15:23:49 +0800
From:	"Jike Song" <albcamus@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Creating dev nodes from driver or via uevent?

On Wed, Oct 15, 2008 at 2:39 PM, Fabiano Sidler <lists@...scode.ch> wrote:
> Hi folks!
>
> Probably a very basic question, but is it better to directly mknod from a
> module's init funtion or to use the uevent/udev mechanism? If the latter,
> are there good overviews, explanations and comprehensive code samples
> especially for using udev,
You can refer to any in-tree driver that calls class_create() and
device_create_drvdata() afterwards.  say drivers/char/raw.c

LDD3 by Greg has some descriptions on this, but since the interface
has changed..

-- 
Thanks,
Jike
--
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/