From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: backes@rhrk.uni-kl.de
Cc: linux-kernel@vger.kernel.org (LINUX Kernel)
Subject: Re: IRQ usage for PCI devices, Kernel 2.4.4
Date: Thu, 17 May 2001 00:22:35 +0100 (BST) [thread overview]
Message-ID: <E150Acl-0004az-00@the-village.bc.nu> (raw)
In-Reply-To: <XFMail.20010516074607.backes@rhrk.uni-kl.de> from "Joachim Backes" at May 16, 2001 07:46:07 AM
> May 13 14:24:41 sunny kernel: PCI: Found IRQ 10 for device 00:0e.0
> May 13 14:24:41 sunny kernel: PCI: The same IRQ used for device 00:0a.0
> "0e" is my PCI sound card, and "0a" is my PCI ethernet card. The messages apppear in
> the following environment: I send from another linux machine (per ssh) a command
> wich plays some sound on my sound card, therefore the eth0 event and the sound
> event occur at almost the same time.
>
> Question: Can I ignore these messages, or is there any buggy behaviour?
This is debugging messages - you can ignore them. PCI supports IRQ sharing
next prev parent reply other threads:[~2001-05-16 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 5:46 IRQ usage for PCI devices, Kernel 2.4.4 Joachim Backes
2001-05-16 23:22 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-16 15:13 Khachaturov, Vassilii
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=E150Acl-0004az-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=backes@rhrk.uni-kl.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