From: Matthew Hall <matt@ecsc.co.uk>
To: Donald Becker <becker@scyld.com>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] sundance on d-link dfe-580tx
Date: 14 Jun 2002 17:06:19 +0100 [thread overview]
Message-ID: <1024070779.972.53.camel@smelly.dark.lan> (raw)
In-Reply-To: <Pine.LNX.4.33.0206131201480.1828-100000@presario>
Sorry to bother you again Donald, but I'm still having problems,
The following error comes up when I make modules with the 1.06 version:
sundance.c: In function `sundance_probe1':
sundance.c:464: `pci_tbl' undeclared (first use in this function)
sundance.c:464: (Each undeclared identifier is reported only once
sundance.c:464: for each function it appears in.)
sundance.c: In function `cleanup_module':
sundance.c:1372: `pci_tbl' undeclared (first use in this function)
make[2]: *** [sundance.o] Error 1
make[2]: Leaving directory `/usr/src/linux/drivers/net'
make[1]: *** [_modsubdir_net] Error 2
make[1]: Leaving directory `/usr/src/linux/drivers'
make: *** [_mod_drivers] Error 2
I've checked the code of sundance.c, pci-scan.h and kern_compat.c and
pci_tbl isn't defined or declared anywhere in these files, am I missing
something else, or going crazy?
Thanks in advance,
Matthew Hall
On Thu, 2002-06-13 at 17:12, Donald Becker wrote:
> You are still running the old driver, not the driver at
> http://www.scyld.com/network/ethercard.html
> ftp://www.scyld.com/pub/network/sundance.c
>
> > Just in case you can provide any more insight into this I compiled the
> > alta-diag tool, for debugging purposes, the results of -aa, -ee and -mm
> > are attached, aswell as the full detection message from dmesg after
> > modprob'ing the module.
>
> I never released a "1.01b" driver in January 2002. The 1.01a driver was
> released about two years ago. The current version is
> sundance.c:v1.06 1/28/2002
>
> The diagnostic program is reading the correct station address, however
> the driver you are using is reading a bogus address. I believe that
> that my driver release should correctly work with this card.
>
next prev parent reply other threads:[~2002-06-14 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 12:43 Matthew Hall
2002-06-12 3:39 ` Donald Becker
2002-06-13 14:57 ` Matthew Hall
2002-06-13 15:34 ` Ben Greear
2002-06-13 16:12 ` Donald Becker
2002-06-14 16:06 ` Matthew Hall [this message]
2002-06-14 21:52 ` Donald Becker
2002-06-21 5:27 ` Jeff Garzik
2002-06-21 12:17 ` Matthew Hall
2002-07-12 2:41 ` kwijibo
2002-06-14 10:15 ` Marcus Sundberg
[not found] ` <1024070521.973.48.camel@smelly.dark.lan>
[not found] ` <vevg8l25uq.fsf@inigo.ingate.se>
2002-06-17 14:58 ` Matthew Hall
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=1024070779.972.53.camel@smelly.dark.lan \
--to=matt@ecsc.co.uk \
--cc=becker@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
all inboxes | Powered by JetHome®