mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: malware@t-online.de (Malware)
To: linux-kernel@vger.kernel.org
Subject: [PATCH] PC keyboard: Disable interrupts during initialization
Date: Sat, 22 Feb 2003 14:42:56 +0100	[thread overview]
Message-ID: <200302221342.h1MDguW0029229@debian.malware.de> (raw)

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.757.40.2 -> 1.757.40.3
#	drivers/char/pc_keyb.c	1.13    -> 1.14   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/02/22	malware@debian.malware.de	1.757.40.3
# pc_keyb.c:
#   Fix: Disable interrupts during keyboard initialization.
#      The initialization does cause keyboard interrupts. On most platforms this
#      should not be a problem. But if there is no interrupt controller the
#      interrupt might retriggered for ever. This happended on the m68k/TekXpress
#      port. 
# --------------------------------------------
#
diff -Nru a/drivers/char/pc_keyb.c b/drivers/char/pc_keyb.c
--- a/drivers/char/pc_keyb.c	Sat Feb 22 13:29:21 2003
+++ b/drivers/char/pc_keyb.c	Sat Feb 22 13:29:21 2003
@@ -898,6 +898,8 @@
 
 void __init pckbd_init_hw(void)
 {
+	unsigned long flags;
+
 	if (!kbd_controller_present()) {
 		kbd_exists = 0;
 		return;
@@ -905,6 +907,9 @@
 
 	kbd_request_region();
 
+	save_flags(flags);
+	cli();
+
 	/* Flush any pending input. */
 	kbd_clear_input();
 
@@ -922,6 +927,8 @@
 
 	/* Ok, finally allocate the IRQ, and off we go.. */
 	kbd_request_irq(keyboard_interrupt);
+
+	restore_flags(flags);
 }
 
 #if defined CONFIG_PSMOUSE

                 reply	other threads:[~2003-02-22 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200302221342.h1MDguW0029229@debian.malware.de \
    --to=malware@t-online.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

all inboxes | Powered by JetHome®