mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>
To: Micah Dowty <micah@navi.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Force feedback support for uinput
Date: Mon, 22 Nov 2004 17:55:15 -0200	[thread overview]
Message-ID: <20041122195515.GF24080@cathedrallabs.org> (raw)
In-Reply-To: <20041122194751.GA30536@navi.cx>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

> On Mon, Nov 22, 2004 at 08:38:01AM -0200, Aristeu Sergio Rozanski Filho wrote:
> > > +The uinput driver creates a character device, usually at /dev/uinput, that can
> > the default is '/dev/input/uinput'
> 
> Really? I haven't tried udev yet (shamefully enough) but with devfs at least
> it shows up as /dev/misc/uinput with a symlink at /dev/uinput.
> 
> If it really can be either /dev/uinput or /dev/input/uinput, I guess the document
> and some of my userspace code needs modifying ;)
well, at least I think everything related to input subsystem should be
inside /dev/input/ and I always did so because it seems more logical.
I guess udev is also using /dev/input/uinput, but I'm not sure.
As soon I finish some user space stuff I'm working on I'll add more
documentation on uinput.txt and check devfs and udev.

-- 
Aristeu


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-11-22 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 16:37 Micah Dowty
2004-11-12 12:09 ` aris
2004-11-21  8:54   ` Micah Dowty
2004-11-22 10:38     ` Aristeu Sergio Rozanski Filho
2004-11-22 19:47       ` Micah Dowty
2004-11-22 19:55         ` Aristeu Sergio Rozanski Filho [this message]

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=20041122195515.GF24080@cathedrallabs.org \
    --to=aris@cathedrallabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=micah@navi.cx \
    /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®