From: Rob Myers <rob.myers@gtri.gatech.edu>
To: Michael Clark <michael@metaparadigm.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
LKML <linux-kernel@vger.kernel.org>,
Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: [PATCH] - 2.4.16 ns83820 optical support (Netgear GA621)
Date: 05 Dec 2001 11:56:59 -0500 [thread overview]
Message-ID: <1007571419.14051.38.camel@ransom> (raw)
In-Reply-To: <3C0E3120.2000504@metaparadigm.com>
In-Reply-To: <3C0CED3B.7030409@metaparadigm.com> <1007501048.14051.28.camel@ransom> <3C0D7CEA.2050307@metaparadigm.com> <3C0E194B.2BB7E289@mandrakesoft.com> <3C0E3120.2000504@metaparadigm.com>
On Wed, 2001-12-05 at 09:37, Michael Clark wrote:
> Problem solved. New patch attached.
ns83820-optical-0.13c.patch works, too. although you forgot to bump the
version letter to c. ;) the versions in the dmesg output below are
correct. (i tested the p2b-d with v0.13c and the cur-dls with v0.13b)
i wonder what implications there are that its trying to do 64bit pci on
the p2b-d board?
thanks again michael, jeff, and ben!
rob.
asus p2b-d dmesg output: (32bit pci slot / redhat 7.2 / 2.4.9 stock
kernel)
eth1: enabling 64 bit PCI.
eth1: enabling optical transceiver
eth1: ns83820.c v0.13c: DP83820 00:40:f4:29:ea:d7 pciaddr=0xe1000000
irq=12 rev 0x103
eth1: link now 1000F mbps, full duplex and up.
asus p2b-d dmesg output: (same 32bit pci slot / 2.4.16)
eth1: enabling 64 bit PCI.
eth1: enabling optical transceiver
eth1: ns83820.c v0.13c: DP83820 00:40:f4:29:ea:d7 pciaddr=0xe1000000
irq=12 rev 0x103
eth1: link now 1000F mbps, full duplex and up.
tyan cur-dls dmesg output: (64bit pci slot / 2.4.16)
eth2: enabling 64 bit PCI.
eth2: enabling optical transceiver
eth2: ns83820.c v0.13b: DP83820 00:40:f4:29:ea:d7 pciaddr=0xf8800000
irq=21 rev 0x103
eth2: link now 1000F mbps, full duplex and up.
tyan cur-dls dmesg output: (32bit pci slot / 2.4.16)
eth2: disabling 64 bit PCI.
eth2: enabling optical transceiver
eth2: ns83820.c v0.13b: DP83820 00:40:f4:29:ea:d7 pciaddr=0xfc000000
irq=17 rev 0x103
eth2: link now 1000F mbps, full duplex and up.
next prev parent reply other threads:[~2001-12-05 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 15:35 [PATCH] - 2.4.16 ns83820 optical support (Netgear GA621) Michael Clark
2001-12-04 21:24 ` Rob Myers
2001-12-04 21:31 ` Jeff Garzik
2001-12-05 1:48 ` Michael Clark
2001-12-05 5:02 ` Michael Clark
2001-12-05 12:55 ` Jeff Garzik
2001-12-05 14:37 ` Michael Clark
2001-12-05 16:56 ` Rob Myers [this message]
2001-12-05 22:50 ` Benjamin LaHaise
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=1007571419.14051.38.camel@ransom \
--to=rob.myers@gtri.gatech.edu \
--cc=bcrl@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.