public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Lamanna <jamesl@appliedminds.com>
To: Sascha Wilde <wilde@sha-bang.de>
Cc: "David N. Welton" <davidw@eidetix.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernel won't reboot on AMD system - 8042 problem?
Date: Tue, 10 Aug 2004 08:38:18 -0700	[thread overview]
Message-ID: <4118EBEA.10809@appliedminds.com> (raw)
In-Reply-To: <20040810093734.GA1089@kenny.sha-bang.local>

Sascha Wilde wrote:
> On Mon, Aug 09, 2004 at 10:28:45AM +0200, David N. Welton wrote:
> 

> 
> Big question:  how was the initialisation of the PS/2 ports managed in
> 2.4.x?  Ther seems to be no similar code to i8042.c in it[0], and all I
> have found till now is a bunch ob obscure jump-rables in
> arch/i386/kernel/setup.c ...

Look at drivers/char/pc_keyb.c
That's where the 2.4.x initialization takes place it seems.
It's pretty generic, but it looks like some of the commands are similar 
in initialize_kbd() - constants are in include/linux/pc_keyb.h

Pretty much all PC hardware has a i8042-like controller, so I think that 
file is the generic PC keyboard startup for i8042-like devices.

Looks like 2.6.x abstracted this a little farther through the serio 
layer, so at initialization, the system tries to assign a particular 
driver to the serio ports it finds (there are drivers for AT, i8042 (and 
variants), etc..)

-- 
James Lamanna

  reply	other threads:[~2004-08-10 15:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <auto-000000462036@appliedminds.com>
2004-08-09  8:28 ` 2.6 kernel won't reboot on AMD system - 8042 problem? David N. Welton
2004-08-10  9:37   ` Sascha Wilde
2004-08-10 15:38     ` James Lamanna [this message]
2004-08-11 14:14 Dmitry Torokhov
2004-08-11 17:56 ` Sascha Wilde
2004-08-12 17:00   ` David N. Welton
2004-08-12 17:23     ` David N. Welton
2004-08-13 21:29       ` Sascha Wilde
2004-08-12 20:13     ` Vojtech Pavlik
2004-08-13 10:13       ` David N. Welton
2004-08-13 12:03         ` Vojtech Pavlik
2004-08-13 12:58           ` David N. Welton
     [not found] <4112A626.1000706@appliedminds.com>
2004-08-06  8:22 ` David N. Welton
2004-08-06 16:55   ` James Lamanna
2004-08-08 12:18   ` Sascha Wilde
2004-08-08 15:05     ` Dmitry Torokhov
2004-08-11 20:06       ` Sascha Wilde
  -- strict thread matches above, loose matches on Subject: below --
2004-07-28 17:51 2.6 kernel won't reboot on AMD system (no, not the BIOS...) David N. Welton
2004-08-05 12:48 ` 2.6 kernel won't reboot on AMD system - 8042 problem? David N. Welton
2004-08-05 19:25   ` Sascha Wilde
2004-08-11  6:31   ` Dmitry Torokhov
2004-08-11  8:36     ` David N. Welton
2004-08-11 12:27     ` Vojtech Pavlik
2004-08-11 12:45       ` David N. Welton
2004-08-11 13:43       ` Sascha Wilde
2004-08-11 14:17         ` Vojtech Pavlik
2004-08-11 13:55       ` David Ford
2004-08-11 20:14     ` Sascha Wilde

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=4118EBEA.10809@appliedminds.com \
    --to=jamesl@appliedminds.com \
    --cc=davidw@eidetix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wilde@sha-bang.de \
    /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