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: <1182437233.2782.36.camel@shinybook.infradead.org>
Date:	Thu, 21 Jun 2007 22:47:12 +0800
From:	David Woodhouse <dwmw2@...radead.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Vojtech Pavlik <vojtech@....cz>
Subject: Re: Writing a driver for a legacy serial device

On Thu, 2007-06-21 at 11:33 +0200, Jean Delvare 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.

You might do better to implement it as a line discipline instead. 
Or just do it in userspace. What exactly are you trying to do?

-- 
dwmw2

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