[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200611121441.16790.arvidjaar@mail.ru>
Date: Sun, 12 Nov 2006 14:41:16 +0300
From: Andrey Borzenkov <arvidjaar@...l.ru>
To: Adrian Bunk <bunk@...sta.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc5: where can I select INPUT?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 11 November 2006 15:30, Adrian Bunk wrote:
> On Sat, Nov 11, 2006 at 03:18:41PM +0300, Andrey Borzenkov wrote:
> > On Saturday 11 November 2006 14:25, Adrian Bunk wrote:
> > > On Sat, Nov 11, 2006 at 01:24:58PM +0300, Andrey Borzenkov wrote:
> > > > Neither in menuconfig nor in xconfig do I see any place to actually
> > > > select INPUT. Help text suggests that it is a) selectable b) it can
> > > > be made modules. I do not have either option. Here what I see in
> > > > menuconfig if I go into Input device support:
> > > >
> > > > --- Generic input layer (needed for keyboard, mouse, ...)
> > > > < > Support for memoryless force-feedback devices
> > > > --- Userland interfaces
> > > >
> > > > as you see there is no check box for INPUT itself.
> > > >
> > > > I already had similar issue something else (I believe it was
> > > > something related to serio). In menuconfig item was no selectable,
> > > > but I could directly edit .config to change y to m.
> > > >...
> > >
> > > INPUT can only be unset if you set CONFIG_EMBEDDED=y.
> >
> > {pts/1}% grep EMB /boot/config
> > CONFIG_EMBEDDED=y
> >
> > > The rationale is that it usually doesn't make sense for users to
> > > disable INPUT, and allowing it tends to cause some confusion.
> >
> > I do not want to disable it. I want to make it module (OK it has the same
> > rationale - if you need it anyway why you do want to make it module etc).
> > This should be possible according to help text. It does not work. Direct
> > editing of .config silently reverts it back to y instead of m.
>
> What you want seems to require some non-trivial changes.
>
> Are you trying this "just because it should work" or is there a strong
> technical reason why you need it?
>
No, I do not have any compelling technical reason; I was just going via more
or less permanent .config cleanup round and was surprised why it did not work
because it did work before (but it was really long ago, I guess in late 2.5
times). When I tried it last time I was mostly driven by attempt to minimize
kernel size so it fitted for floppy boot. Since then it became less
interesting (it is probably won't fit anymore and distribution I use dropped
floppy boot support anyway).
Thank you (and Russel) for explanation and sorry if it was too trivial
question.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFVwhcR6LMutpd94wRAkddAJ0aJls5N7/LXnCPBt34EOlXiDXaVgCgiSx7
RNd079+8bvlJ/UdXN5DiDw0=
=mEtn
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists