From: Vojtech Pavlik <vojtech@suse.cz>
To: Tuukka Toivonen <tuukkat@ee.oulu.fi>
Cc: Sau Dan Lee <danlee@informatik.uni-freiburg.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: SERIO_USERDEV patch for 2.6
Date: Thu, 3 Jun 2004 23:23:25 +0200 [thread overview]
Message-ID: <20040603212325.GB1065@ucw.cz> (raw)
In-Reply-To: <Pine.GSO.4.58.0406031241330.8752@stekt37>
On Thu, Jun 03, 2004 at 01:21:21PM +0300, Tuukka Toivonen wrote:
> New version released which addresses the issues you mentioned:
> wget \
> http://www.ee.oulu.fi/~tuukkat/tmp/linux-2.6.6-userdev.20040603.patch
>
> >On Sun, 30 May 2004, Vojtech Pavlik wrote:
> >>Coexisting would mean that when someone wants to open the raw device,
> >>the serio layer would disconnect the psmouse driver, and give control to
> >>the raw device instead. I believe that could work.
>
> Done, with slight modification: if the device is opened in read-only mode,
> the kernel drivers are not disconnected. This way the serio port could be
> controlled via IOCTL even when assigned to kernel drivers, if it ever
> becomes useful. Useful also for debugging etc.
>
> >>I'd like to keep it separate from the
> >>serio.c file, although it's obvious it'll require to be linked to it
> >>statically, because it needs hooks there
>
> Done. It's now in serio-dev.c. I also added serio-dev.h, which
> unfortunately is slightly messy so that I was able to inline some
> functions. It would be trivial to clean it up, if I wouldn't inline
> those functions.
>
> I also had to rename serio.c into serio-core.c, which makes the actual
> changes into the file unobvious from the patch above. I made a separate
> diff about that, shown below (just for easy comparison).
>
> The last change I made converts slashes '/' into underscores '_' (so
> eg. isa0060/serio0 is changed to isa0060_serio0 in /proc/misc, /dev
> with devfs, and /sys) because Sau Dan Lee reported that slashes don't work
> well with sysfs.
>
> I tested the patch in a couple of machines, especially the new features.
> Seems to work finely.
I like it. Give me a while to evaluate your and Dmitry's approach in
relation to future ...
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-06-03 21:22 UTC|newest]
Thread overview: 32+ 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 [this message]
2004-06-01 16:50 ` Sau Dan Lee
2004-06-01 18:18 ` Dmitry Torokhov
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
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=20040603212325.GB1065@ucw.cz \
--to=vojtech@suse.cz \
--cc=danlee@informatik.uni-freiburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tuukkat@ee.oulu.fi \
/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
all inboxes | Powered by JetHome®