linux-kernel - Re: Writing a driver for a legacy serial 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]

Message-ID: <d120d5000706221247g618fffadh2c4296aa62a39b9e@mail.gmail.com>
Date:	Fri, 22 Jun 2007 15:47:43 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Jean Delvare" <khali@...ux-fr.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Vojtech Pavlik" <vojtech@....cz>
Subject: Re: Writing a driver for a legacy serial device

On 6/21/07, Jean Delvare <khali@...ux-fr.org> wrote:
>
> OK. This leads me to a question: is it OK for me to add support for my
> non-input device to inputattach, or is a separate, dedicated helper
> tool preferred? Both ways are fine with me, I don't know what the input
> subsystem maintainers expect.
>

Your device does not need any initialization done by userspace, does
it? How widespread is this device? inputattach has "--dump" option
which sets up a SERIO_RS232/0/0/0 serio port. You could mark your
serio driver as manual bind driver and bind it trhough sysfs (echo -n
"taos-evm" /sys/device/serio/devices/serioX/drvctl to bind it).

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