From: Marcel Holtmann <marcel@holtmann.org>
To: "P.Manohar" <pmanohar@lantana.cs.iitm.ernet.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ioctl to keyboard device file
Date: Wed, 11 May 2005 19:53:20 +0200 [thread overview]
Message-ID: <1115834000.23458.77.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.60.0505112301350.31722@lantana.cs.iitm.ernet.in>
Hi,
> >> I want to add a new ioctl to keyboard driver device file which will
> >> perform the work of copying user space data sent to it into kernel
> >> space and send those characters to handle_scancode function of keyboard
> >> driver.. Now I want to know
> >>
> >> 1) what is the device file corresponding to keyboard (is it
> >> /dev/input/keyboard).
> >> 2) where file operations structure is defined for that.
> >> 3) where the those ioctls handled(not found in keyboard.c).
> >>
> >> Any small help is appreciated.
> >
> > why not using uinput for this job?
>
> Thanks for the solution. I did the above task, by defining a new
> character device driver and sending ioctl to it. and calling
> handle_scancode from it. Now I want
> to do the same task with in the keyboard driver. For that I need to send
> ioctl to keyboard device file.
> For that only I asked the
> above doubts.
what your are trying to do looks wrong to me. Why don't you use uinput.
It is there and it is the correct thing for the job.
Regards
Marcel
next prev parent reply other threads:[~2005-05-11 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 16:43 ioctl to keyboard device file P.Manohar
2005-05-11 17:14 ` Marcel Holtmann
2005-05-11 17:34 ` P.Manohar
2005-05-11 17:53 ` Marcel Holtmann [this message]
2005-05-11 18:17 ` Jan-Benedict Glaw
[not found] ` <Pine.LNX.4.60.0505121454240.26644@lantana.cs.iitm.ernet.in>
2005-05-12 10:01 ` Marcel Holtmann
2005-05-16 8:58 ` P.Manohar
2005-05-16 9:54 ` Marcel Holtmann
[not found] ` <Pine.LNX.4.60.0505162112240.25368@lantana.cs.iitm.ernet.in>
2005-05-16 16:19 ` Marcel Holtmann
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=1115834000.23458.77.camel@pegasus \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmanohar@lantana.cs.iitm.ernet.in \
/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