From: FabF <fabian.frederick@skynet.be>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel 2.6.7 Shows Two i8042's in /proc/interrupts?
Date: Tue, 29 Jun 2004 19:03:31 +0200 [thread overview]
Message-ID: <1088528611.3526.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0406291231040.10973@p500>
On Tue, 2004-06-29 at 18:32, Justin Piszcz wrote:
> I have APIC+ACPI+/dev/rtc enabled.
>
> Curious though, why two i8042's?
>
> $ uname -a
> Linux 2.6.7 #2 SMP Tue Jun 22 18:19:08 EDT 2004 i686 unknown unknown GNU/Linux
>
> $ gcc -v
> Reading specs from
> /a/app/gcc-3.4.0/bin/../lib/gcc/i686-pc-linux-gnu/3.4.0/specs
> Configured with: ./configure --prefix=/app/gcc-3.4.0
> Thread model: posix
> gcc version 3.4.0
>
> # cat /proc/interrupts
> CPU0 CPU1
> 0: 30593638 0 IO-APIC-edge timer
> 1: 7228 0 IO-APIC-edge i8042
> 8: 130233 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-level acpi
> 12: 87258 0 IO-APIC-edge i8042
> 14: 38 0 IO-APIC-edge ide0
> 15: 72 0 IO-APIC-edge ide1
> 16: 3967335 0 IO-APIC-level nvidia
> 18: 3431241 0 IO-APIC-level eth0
> 20: 401933 0 IO-APIC-level ide2
> 21: 23832 0 IO-APIC-level EMU10K1
> NMI: 0 0
> LOC: 30594585 30594625
> ERR: 0
> MIS: 0
Same behaviour for a while Justin.I guess second one is used for mouse.
Regards,
FabF
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2004-06-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 16:32 Linux Kernel 2.6.7 Shows Two i8042's in /proc/interrupts? Justin Piszcz
2004-06-29 16:57 ` Dave Jones
2004-06-29 17:03 ` FabF [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=1088528611.3526.5.camel@localhost.localdomain \
--to=fabian.frederick@skynet.be \
--cc=jpiszcz@lucidpixels.com \
--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