linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.32 doesn't beep?
Date: 29 Aug 2002 08:41:41 GMT	[thread overview]
Message-ID: <slrnamrni5.3ub.kraxel@bytesex.org> (raw)
In-Reply-To: 20020828223005.A21207@ucw.cz

> > Another issue: I enabled CONFIG_INPUT_MOUSEDEV_PSAUX, but /dev/psaux
> > gave an ENODEV when opened. Turns out CONFIG_INPUT_MOUSEDEV is
> > also required, but for some reason 'make config' let me set the
> > former without also setting the latter. A bug in input's config.in?
>  
>  Yes, a bug. Fixed now.

input in 2.5.32 also doesn't work fully modular because of some
unresolved symbols.  I fixed it this way:

==============================[ cut here ]==============================
--- linux-2.5.32/drivers/char/keyboard.c	Wed Aug 28 16:10:33 2002
+++ linux/drivers/char/keyboard.c	Wed Aug 28 16:11:43 2002
@@ -66,6 +66,7 @@
 #endif
 
 struct pt_regs *kbd_pt_regs;
+EXPORT_SYMBOL(kbd_pt_regs);
 void compute_shiftstate(void);
 
 /*
--- linux-2.5.32/drivers/input/input.c	Wed Aug 28 16:21:14 2002
+++ linux/drivers/input/input.c	Wed Aug 28 16:21:40 2002
@@ -772,6 +772,7 @@
 struct device_class input_devclass = {
 	.name		= "input",
 };
+EXPORT_SYMBOL(input_devclass);
 
 static int __init input_init(void)
 {
==============================[ cut here ]==============================

  Gerd

-- 
You can't please everybody.  And usually if you _try_ to please
everybody, the end result is one big mess.
				-- Linus Torvalds, 2002-04-20

  reply	other threads:[~2002-08-29  8:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:47 Linux v2.5.32 Linus Torvalds
2002-08-27 20:22 ` Stephane Wirtel
2002-08-27 20:36   ` Thunder from the hill
2002-08-27 20:48     ` Stephane Wirtel
2002-08-27 20:54   ` Gabor Z. Papp
2002-08-28  6:18     ` Jan-Benedict Glaw
2002-08-28  7:41       ` Edward Coffey
2002-08-28  8:35       ` Russell King
2002-08-27 20:43 ` Udo A. Steinberg
2002-08-27 20:47   ` Andre Hedrick
2002-08-27 20:47   ` Alexander Viro
2002-08-27 22:35     ` Alan Cox
2002-08-28  2:07       ` [PATCH] " Alexander Viro
2002-08-28  1:21     ` Arador
2002-08-28  2:17       ` Alexander Viro
2002-08-27 22:28 ` Chris Funderburg (at home)
2002-08-28  7:31 ` Linux v2.5.32 - some menuconfig oddities Helge Hafting
2002-08-28  7:43   ` Gabor Kerenyi
2002-08-28  8:14 ` Linux v2.5.32 Edward Coffey
2002-08-28  8:17   ` Writing files to remote storage Kevin Liao
2002-08-28 14:18     ` Alan Cox
2002-08-28 13:00 ` 2.5.32 doesn't beep? Mikael Pettersson
2002-08-28 13:05   ` Vojtech Pavlik
2002-08-28 13:12     ` Mikael Pettersson
2002-08-28 13:58     ` Gerhard Mack
2002-08-28 14:33       ` Jos Hulzink
2002-08-28 14:49       ` Vojtech Pavlik
2002-08-28 20:04     ` Mikael Pettersson
2002-08-28 20:30       ` Vojtech Pavlik
2002-08-29  8:41         ` Gerd Knorr [this message]
2002-08-28 17:21 ` Linux v2.5.32 Adrian Bunk
2002-08-31 16:54 ` Linux v2.5.32 (Config options to have a working keyboard) Axel Siebenwirth

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=slrnamrni5.3ub.kraxel@bytesex.org \
    --to=kraxel@bytesex.org \
    --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;
as well as URLs for NNTP newsgroup(s).