From: Linus Torvalds <torvalds@transmeta.com>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
andrewm@uow.edu.au, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 3c59x: Using bad IRQ 0
Date: Thu, 23 Nov 2000 09:06:45 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10011230901580.7992-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011212252300.30223-300000@svea.tellus>
On Tue, 21 Nov 2000, Tobias Ringstrom wrote:
> >
> > Tobias, can you confirm that calling pci_enable_device before reading
> > dev->irq fixes the 3c59x.c problem for you?
>
> Nope. The interrupts do not seem to get through. Packets are transmitted,
> but that's it. I've copied the interesting parts from dmesg:
>
> 3c59x.c:LK1.1.11 13 Nov 2000 Donald Becker and others. http://www.scyld.com/network/vortex.html $Revision: 1.102.2.46 $
> See Documentation/networking/vortex.txt
> PCI: Enabling device 00:0a.0 (0014 -> 0017)
> PCI: Assigned IRQ 9 for device 00:0a.0
> eth0: 3Com PCI 3c905C Tornado at 0xa400, 00:01:02:b4:18:e4, IRQ 9
Ok, the VIA stuff is happy, and enables the irq routing. The fact that the
irq's don't actually seem to ever actually appear means that the enable
sequence is probably slightly buggy.
Can you do two things?
- enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code
print out what the pirq table entries are etc.
- add the line "eisa_set_level_irq(irq);" to pirq_via_set() just before
the "return 1;"
Jeff, you had complete VIA docs, right? Can you check that whatever
Tobias' ends up having output from the debug stuff looks sane?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 19:09 3c59x: Using bad IRQ 0 Tobias Ringstrom
2000-11-21 19:28 ` Jeff Garzik
2000-11-21 22:18 ` Tobias Ringstrom
2000-11-23 17:06 ` Linus Torvalds [this message]
2000-11-23 18:21 ` Tobias Ringstrom
2000-11-23 18:32 ` Linus Torvalds
2000-11-24 0:14 ` Jeff Garzik
2000-11-22 1:26 ` Linus Torvalds
2000-11-24 14:59 ` Erik Mouw
2000-11-24 23:14 ` Jeff Garzik
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=Pine.LNX.4.10.10011230901580.7992-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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;
as well as URLs for NNTP newsgroup(s).