From: Christopher Keller <cnkeller@interclypse.net>
To: linux-kernel@vger.kernel.org
Subject: 3COM 3C990 NIC
Date: 18 Oct 2002 21:49:36 -0700 [thread overview]
Message-ID: <1035002976.3086.4.camel@maranello.interclypse.net> (raw)
Is anyone maintaining the 3C990 driver? I'm using the code from 3COM and
it doesn't look like it's been kept up to date with the various kernel
changes. I'm also using the latest Red Hat kernel in case it matters.
When compiling with SMP support, I'm getting the following errors during
a depmod -ae
depmod: *** Unresolved symbols in
/lib/modules/2.4.18-17.8.0smp/kernel/drivers/net/3c990.o
depmod: pci_write_config_byte
depmod: eth_type_trans
depmod: __wake_up
depmod: __kfree_skb
depmod: alloc_skb
depmod: init_etherdev
depmod: kmalloc
depmod: pci_free_consistent
depmod: pci_find_class
depmod: pci_read_config_byte
depmod: cpu_raise_softirq
depmod: free_irq
depmod: unregister_netdev
depmod: __out_of_line_bug
depmod: iounmap
depmod: pci_alloc_consistent
depmod: interruptible_sleep_on_timeout
depmod: __ioremap
depmod: pci_read_config_word
depmod: kfree
depmod: request_irq
depmod: netif_rx
depmod: skb_over_panic
depmod: jiffies
depmod: softnet_data
depmod: printk
depmod: __const_udelay
I get no problems in the single processor compile & depmod. Can these be
safely ignored? The SMP #define simply includes the spinlock stuff.
#ifdef SMP
#include <linux/spinlock.h>
#endif
--
Homepage: http://interclypse.net
Registered Linux user #215241 (http://counter.li.org/)
next reply other threads:[~2002-10-19 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 4:49 Christopher Keller [this message]
2002-10-22 4:54 ` 3COM 3C990 NIC David Dillow
2002-10-22 9:47 ` Jeff Garzik
2002-10-22 14:53 ` David Dillow
2002-10-22 14:37 ` Christopher Keller
2002-10-22 23:13 ` David S. Miller
2002-10-23 3:50 ` David Dillow
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=1035002976.3086.4.camel@maranello.interclypse.net \
--to=cnkeller@interclypse.net \
--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