public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Daniel Egger <degger@fhm.edu>, linux-kernel@vger.kernel.org
Subject: Re: IRQ Routing Conflict
Date: Sat, 9 Nov 2002 10:30:32 +0100	[thread overview]
Message-ID: <20021109093031.GC4563@fs.tum.de> (raw)
In-Reply-To: <20021107195343.GA961@chiara.cavy.de>

On Thu, Nov 07, 2002 at 08:53:43PM +0100, Heinz Diehl wrote:
> On Sat Nov 02 2002, Daniel Egger wrote:
> 
> > Nov  1 16:10:20 nicole kernel: solo1: version v0.19 time 11:19:52 Apr 14 2002
> > Nov  1 16:10:20 nicole kernel: PCI: Found IRQ 10 for device 00:13.0
> > Nov  1 16:10:20 nicole kernel: IRQ routing conflict for 00:13.0, have irq 3, want irq 10
>  
> > This is also an Apollo/MVP3 chipset. Other than that the soundcard seems
> > to work fine.
> 
> Just to mention it: my network card also works flawlessly with this
> curious "irq routing conflict"....

<AOL>

PCI: Found IRQ 11 for device 00:0a.0
IRQ routing conflict for 00:0a.0, have irq 10, want irq 11
eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 00:40:05:32:EB:19.


The card works fine, this is on a MVP3 running 2.4.20-rc1.

</AOL>

> Greetings, Heinz.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2002-11-09  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 22:36 IRQ Routing Conflict Heinz Diehl
2002-11-01 23:42 ` Daniel Egger
2002-11-07 19:53   ` Heinz Diehl
2002-11-09  9:30     ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-23 10:58 IRQ routing conflict Marko Rauhamaa
2002-01-24  0:18 ` Erik Mouw
2002-01-24 10:43 ` Rob Landley

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=20021109093031.GC4563@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=degger@fhm.edu \
    --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