public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] Kconfig: cleanup input menu
Date: Sat, 29 Jan 2005 18:40:12 -0500	[thread overview]
Message-ID: <200501291840.12694.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0501300008381.6118@scrub.home>

On Saturday 29 January 2005 18:20, Roman Zippel wrote:
> Hi,
> 
> On Sat, 29 Jan 2005, Dmitry Torokhov wrote:
> 
> > On Saturday 29 January 2005 17:20, Roman Zippel wrote:
> > > --- linux-2.6.11.orig/drivers/input/serio/Kconfig       2005-01-29 22:50:43.404946203 +0100
> > > +++ linux-2.6.11/drivers/input/serio/Kconfig    2005-01-29 22:56:42.549085439 +0100
> > > @@ -3,6 +3,7 @@
> > >  #
> > >  config SERIO
> > >         tristate "Serial i/o support" if EMBEDDED || !X86
> > > +       depends on INPUT
> > 
> > ????
> > 
> > serio_raw works fine without INPUT.
> 
> All current serio users depend on INPUT, it's maybe not a strict 
> dependency, but it pretty much needs INPUT anyway to be usable, so I don't 
> see the problem.
> The alternative is to move it completely out of the input menu, if it's 
> really that important for the user being able to select it without input.
> 

I can assure you that serio_raw driver _does not_ use input system - it is
implementation of pre 2.6 /dev/psaux interface giving you access to raw AUX
data. It was written so we can still use PS/2 devices for which we don't have
proper in-kernel driver but have working userspace solution. It completely
bypasses input layer.
 
-- 
Dmitry

  reply	other threads:[~2005-01-29 23:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29 22:20 [PATCH 6/8] Kconfig: cleanup input menu Roman Zippel
2005-01-29 22:50 ` Dmitry Torokhov
2005-01-29 23:20   ` Roman Zippel
2005-01-29 23:40     ` Dmitry Torokhov [this message]
2005-01-29 23:56       ` Roman Zippel
2005-01-30  0:32         ` Dmitry Torokhov
2005-01-30  1:16           ` Roman Zippel
2005-01-30  2:27             ` Dmitry Torokhov
2005-01-30  3:22               ` Roman Zippel
2005-01-30  4:07                 ` Dmitry Torokhov
2005-01-30 15:45                   ` Roman Zippel
2005-01-30 23:39                     ` Dmitry Torokhov
2005-02-04 13:14                       ` Vojtech Pavlik
2005-02-04 13:51                         ` Dmitry Torokhov
2005-02-04 13:58                           ` Vojtech Pavlik
2005-02-04 14:13                         ` Roman Zippel
2005-02-04 14:27                           ` Dmitry Torokhov
2005-02-04 14:47                             ` Roman Zippel
2005-02-04 14:42                     ` Vojtech Pavlik

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=200501291840.12694.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.org \
    /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