From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc5: where can I select INPUT?
Date: Sun, 12 Nov 2006 14:41:16 +0300 [thread overview]
Message-ID: <200611121441.16790.arvidjaar@mail.ru> (raw)
In-Reply-To: <20061111123033.GZ4729@stusta.de>
-----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-----
prev parent reply other threads:[~2006-11-12 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 10:24 2.6.19-rc5: where can I select INPUT? Andrey Borzenkov
2006-11-11 10:30 ` Robert P. J. Day
2006-11-11 11:25 ` Adrian Bunk
2006-11-11 12:18 ` Andrey Borzenkov
2006-11-11 12:28 ` Russell King
2006-11-11 12:30 ` Adrian Bunk
2006-11-12 11:41 ` Andrey Borzenkov [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=200611121441.16790.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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