From: Vojtech Pavlik <vojtech@suse.cz>
To: sting sting <zstingx@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: keyboard and mouse driver module and lsmod in 2.6
Date: Sun, 15 Feb 2004 09:11:35 +0100 [thread overview]
Message-ID: <20040215081135.GC314@ucw.cz> (raw)
In-Reply-To: <Sea2-F67YP0QzBxhJTA00015551@hotmail.com>
On Sun, Feb 15, 2004 at 09:19:46AM +0200, sting sting wrote:
> Hello ,
> In 2.4, when you performed lsmod after boot (and after entering X Windows)
> , if you had performed lsmod you had found that "keybdev" and "mousedev"
> modules
> are loaded in momeory.
>
> in 2.4, the keybdev.c was under
> /linux-2.4-xxx/drivers/input/keybdev.c
>
> Now, in 2.6 ,there is no keybdev.c and I assume there is also no keybdev.o
> (am I right?
> I am not sure).
> On the other hand there is both /drivers/char/keyboard.c
> in 2.6 and 2.4 .
>
> My question is :
> in 2.6, after boot and after starting x windows, when typing lsmod -
> what should be the parallel of keybdev.o ?
>
> (I don't have in my 2.6, under /lib/modules/..., keybdev.o ; was I wrong
> in my configuration?)
>
> even that I have no keybdev.o in my 2.6, ye the keyboard responds (at least
> for some minutes in the beginning).
> Or in 2.6 the keyboard driver is part of the kernel?).
In 2.6 keybdev.c is gone and it's functionality was put into keyboard.c
> and also - what is the parallel of mousedev.o ?
> I ***DO**** have mosedev.o under /drivers/input/mosedev.o but ***NOT***
> under
> the /lib/modules/2.6.0./.....
>
> and also lsmod does not show mousedv.
mousedev on the other hand is still present in 2.6. Maybe you just did
not enable it.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2004-02-15 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 7:19 keyboard and mouse driver module and lsmod in 2.6 sting sting
2004-02-15 8:11 ` Vojtech Pavlik [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=20040215081135.GC314@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=zstingx@hotmail.com \
/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