From: octave klaba <oles@ovh.net>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: eepro100@scyld.com, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18p18 eepro100 issues (packets per irq, shared irqs)
Date: Wed, 01 Nov 2000 21:47:45 +0100 [thread overview]
Message-ID: <3A008171.19F8456B@ovh.net> (raw)
In-Reply-To: <E13r4Kv-0000nC-00@the-village.bc.nu>
> > They share an irq, no matter if I'm using intels e100.o driver or the stock
> > linux one. For performance reasons, can I make them each have a different
> > irq? Doing it from ifconfig gives me a notsupported error, with either
> > driver.
>
> Under 2.2 no. Under 2.4 maybe
one question: using driver 1.11 of eepro, on a server with 1
network carte only, we have something really dirty in dmesg
it writes IRQ 20 !? why all this folks ? ;)
the good news there is no more eth0 problems :)
Octave
IRQ to pin mappings:
IRQ0 -> 2
IRQ1 -> 1
IRQ3 -> 3
IRQ4 -> 4
IRQ5 -> 5
IRQ6 -> 6
IRQ7 -> 7
IRQ8 -> 8
IRQ9 -> 9
IRQ14 -> 14
IRQ16 -> 0
IRQ20 -> 4
IRQ24 -> 8
IRQ25 -> 9
eth0: OEM i82557/i82558 10/100 Ethernet at 0xf0002000, 00:E0:18:02:15:02, IRQ 20.
Board assembly 668081-002, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Receiver lock-up workaround activated.
eepro100.c:v1.11 7/19/2000 Donald Becker <becker@scyld.com>
http://www.scyld.com/network/eepro100.html
eth1: OEM i82557/i82558 10/100 Ethernet at 0xf0004000, 00:E0:18:02:15:02, IRQ 20.
[...]
eth7: OEM i82557/i82558 10/100 Ethernet at 0xf0010000, 00:E0:18:02:15:02, IRQ 20.
Board assembly 668081-002, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Receiver lock-up workaround activated.
eepro100.c:v1.11 7/19/2000 Donald Becker <becker@scyld.com>
http://www.scyld.com/network/eepro100.html
-
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/
prev parent reply other threads:[~2000-11-01 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 19:35 2.2.18p18 eepro100 issues (packets per irq, shared irqs) KJ Pickett
2000-11-01 20:18 ` Alan Cox
2000-11-01 20:47 ` octave klaba [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=3A008171.19F8456B@ovh.net \
--to=oles@ovh.net \
--cc=eepro100@scyld.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