From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Sau Dan Lee <danlee@informatik.uni-freiburg.de>,
Tuukka Toivonen <tuukkat@ee.oulu.fi>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: SERIO_USERDEV patch for 2.6
Date: Tue, 1 Jun 2004 13:18:36 -0500 [thread overview]
Message-ID: <200406011318.36992.dtor_core@ameritech.net> (raw)
In-Reply-To: <xb7n03n5iji.fsf@savona.informatik.uni-freiburg.de>
On Tuesday 01 June 2004 11:50 am, Sau Dan Lee wrote:
>
> Tuukka> Dmitry suggested adding a kernel parameter to specify
> Tuukka> which ports would allow to be read in raw mode and which
> Tuukka> would be handled by kernel drivers.
>
> That means changes have to be made to ALL drivers. That looks "ugly".
That is only an interim solution that will be used until we have proper
sysfs support and are able to re-bind a specific driver to a specific
port. And it seems that only i8042 needs to be changed. As I said before
serial ports still accessible via /dev/ttySx, and other architectures that
provide access to SERIO_8042 type ports have much less diverse set of
peripherials... The changes can be made on as-needed basis.
So the cons of my proposal:
- Drivers need to be modified but changes are very limited.
Pros of my proposal:
- Completely non-intrusive as far as serio subsystem goes.
- The rawdev serio driver can still be used later when we have sysfs.
>
>
> Tuukka> In my opinion, almost the same is achieved more
> Tuukka> conveniently by handling in raw mode simply exactly those
> Tuukka> ports that are opened from userspace (ie. "cat serio1"
> Tuukka> would disconnect kernel driver), and everything else by
> Tuukka> kernel drivers. No additional parameters would be then
> Tuukka> necessary, nor module reloads to change anything.
>
> I have a suggestion using sysfs or procfs:
>
> In some directory (e.g. /proc/input/serio):
>
> unbound_ports/ (contains a pseudo file for each serio port
> that is not attached to any device yet)
> keyboards/ (contains a pseudo file for each serio port
> that is attached to the keyboard device)
> mice/ (contains a pseudo file for each serio port
> attached to mousedev.ko)
> touchscreens/ (contains a pseudo file for each serio port
> attached to tsdev.ko)
> direct/ (contains a pseudo file for each serio port
> that is exposed to userland (currently via "misc")
> directly, RAW)
> etc. The contents of the pseudo files are unimportant. (We could use
> it to show useful info, though.)
>
> Initially, all serio ports have their corresponding pseudofiles
> created under "unbound_ports". When a serio device module
> (e.g. mousedev) is loaded, the module, in the current implementation,
> will attach all mouse device to it. So, the corresponding entries in
> "unbound_ports/" will be moved to "mice/".
>
> If we now want the PS AUX port to be accessed directly, we do a "mv
> unbound_ports/isa0060.serio1 direct/". The serio port isa0060/serio1
Using mv would be implementation trouble, i would rahter do:
echo "rawdev" > /sys/bus/serio/devices/serio0/driver
or something alont these lines. At least that's my grand plan ;)
--
Dmitry
next prev parent reply other threads:[~2004-06-01 18:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 10:39 keyboard problem with 2.6.6 Sau Dan Lee
2004-05-30 11:18 ` Vojtech Pavlik
2004-05-30 11:40 ` Sau Dan Lee
2004-05-30 11:53 ` Russell King
2004-05-30 12:43 ` Vojtech Pavlik
2004-05-30 13:25 ` Sau Dan Lee
2004-05-30 13:42 ` SERIO_USERDEV patch for 2.6 Vojtech Pavlik
2004-05-30 15:09 ` Dmitry Torokhov
2004-05-30 15:58 ` Vojtech Pavlik
2004-05-30 16:10 ` Giuseppe Bilotta
2004-05-30 21:00 ` Vojtech Pavlik
2004-05-31 12:43 ` Giuseppe Bilotta
2004-05-30 16:16 ` Dmitry Torokhov
2004-05-30 20:51 ` Vojtech Pavlik
2004-05-30 23:50 ` Dmitry Torokhov
2004-05-31 6:30 ` Vojtech Pavlik
2004-06-01 8:18 ` Tuukka Toivonen
2004-06-03 10:21 ` [PATCH] " Tuukka Toivonen
2004-06-03 12:21 ` Sau Dan Lee
2004-06-03 13:46 ` Luciano Moreira - igLnx
2004-06-03 21:23 ` Vojtech Pavlik
2004-06-01 16:50 ` Sau Dan Lee
2004-06-01 18:18 ` Dmitry Torokhov [this message]
2004-06-01 22:23 ` Giuseppe Bilotta
2004-06-01 23:50 ` Dmitry Torokhov
2004-06-02 15:08 ` Giuseppe Bilotta
2004-06-01 21:01 ` keyboard problem with 2.6.6 jsimmons
2004-06-01 21:12 ` Valdis.Kletnieks
2004-05-30 13:54 ` Eduard Bloch
2004-05-30 14:03 ` Vojtech Pavlik
2004-06-01 21:03 ` jsimmons
2004-06-04 14:11 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 15:31 SERIO_USERDEV patch for 2.6 Dmitry Torokhov
2004-06-03 13:11 ` Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406011318.36992.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=danlee@informatik.uni-freiburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tuukkat@ee.oulu.fi \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox