2.6.19-rc5: where can I select INPUT?

2.6.19-rc5: where can I select INPUT?

[Andrey Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

This may be related to

  Symbol: INPUT [=y]
  Prompt: Generic input layer (needed for keyboard, mouse, ...)
    Defined at drivers/input/Kconfig:7
    Depends on: EMBEDDED
    Location:
      -> Device Drivers
        -> Input device support
    Selected by: VT

and CONFIG_VT is indeed y (I do not think this even can ever be m). Still even 
then this is way too confusing.
.config can be provided on request

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVaT+R6LMutpd94wRAlwlAJ9RduOcCi3u00p/BsY/GoP2Xs4IgACfV6lp
YqEaBKJ1DY5OK5TIEsH2iP4=
=kBNh
-----END PGP SIGNATURE-----

Re: 2.6.19-rc5: where can I select INPUT?

[Robert P. J. Day]

On Sat, 11 Nov 2006, Andrey Borzenkov wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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.

... snip ...

somewhat off-topic, but when one has questions about oddities in the
configuration process, is it more appropriate to ask on *this* list,
or on the kbuild-devel list?

only two minutes ago, i posted this kind of question to kbuild-devel,
but now i'm wondering if i sent it to the wrong place.  thoughts?

rday

Re: 2.6.19-rc5: where can I select INPUT?

[Adrian Bunk]

On Sat, Nov 11, 2006 at 01:24:58PM +0300, Andrey Borzenkov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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.

The rationale is that it usually doesn't make sense for users to disable 
INPUT, and allowing it tends to cause some confusion.

> - -andrey

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 2.6.19-rc5: where can I select INPUT?

[Andrey Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 11 November 2006 14:25, Adrian Bunk wrote:
> On Sat, Nov 11, 2006 at 01:24:58PM +0300, Andrey Borzenkov wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > 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.

TIA

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVb+iR6LMutpd94wRAtq+AJ0aMam9gJKSCN4PEbVKTEX7aijibgCfbB4/
7yVO9PFy9mQgpU4v2yieaUc=
=WNXy
-----END PGP SIGNATURE-----

Re: 2.6.19-rc5: where can I select INPUT?

[Russell King]

On Sat, Nov 11, 2006 at 03:18:41PM +0300, Andrey Borzenkov wrote:
> On Saturday 11 November 2006 14:25, Adrian Bunk wrote:
> > 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.

Welcome to the wonderful world of the 'select' kconfig statement.

config VT
        bool "Virtual terminal" if EMBEDDED
        select INPUT
        default y if !VIOCONS

This means if VT is selected, INPUT has to be 'y'.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

Re: 2.6.19-rc5: where can I select INPUT?

[Adrian Bunk]

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?

> TIA
> - -andrey

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 2.6.19-rc5: where can I select INPUT?

[Andrey Borzenkov]

-----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-----