From: "David S. Miller" <davem@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lcaron@apartia.fr, linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Tue, 24 Aug 2004 11:34:07 -0700 [thread overview]
Message-ID: <20040824113407.287f0408.davem@redhat.com> (raw)
In-Reply-To: <20040824092533.65cb32da.rddunlap@osdl.org>
On Tue, 24 Aug 2004 09:25:33 -0700
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
> | --------------
> | drivers/net/net.o(.text+0x17550): In function `tg3_request_firmware': :
> | undefined reference to `request_firmware'
> | drivers/net/net.o(.text+0x17652): In function `tg3_request_firmware': :
> | undefined reference to `release_firmware'
> | -------------
> |
> | Any clue?
> |
> | PS: I can include a part of my .config
>
> You need to enable CONFIG_EXPERIMENTAL and CONFIG_HOTPLUG
> and then CONFIG_FW_LOADER in the Library routines menu.
Oh on the contrary, I've never seen a call to request_firmware()
in any copy of the tg3 driver and that's strange being that I'm
the maintainer. :-)
People, if you're going to use patched up kernels, report your
problems to the people you got the kernel from. Thanks.
next prev parent reply other threads:[~2004-08-24 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:13 TG3(Tigoon) & Kernel 2.4.27 Laurent CARON
2004-08-24 16:25 ` Randy.Dunlap
2004-08-24 18:34 ` David S. Miller [this message]
2004-08-25 1:37 ` Joshua Kwan
2004-08-25 3:17 ` Randy.Dunlap
2004-08-25 4:02 ` Joshua Kwan
2004-08-25 4:45 ` Willy Tarreau
2004-08-25 6:36 ` David S. Miller
2004-08-25 7:47 ` Joshua Kwan
2004-08-25 8:34 ` Oliver Neukum
2004-08-25 19:03 ` David S. Miller
2004-08-31 1:14 ` Ryan Cumming
2004-08-31 1:33 ` David S. Miller
2004-08-31 5:05 ` Willy Tarreau
2004-08-25 7:40 ` Laurent CARON
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 22:16 Nathanael Nerode
2004-08-30 22:23 ` Jeff Garzik
2004-08-30 22:31 ` David S. Miller
2004-08-30 22:32 ` Andreas Schwab
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=20040824113407.287f0408.davem@redhat.com \
--to=davem@redhat.com \
--cc=lcaron@apartia.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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