From: "Ruurd A. Reitsma" <R.A.Reitsma@wbmt.tudelft.nl>
To: "Keith Owens" <kaos@ocs.com.au>, "Miles Lane" <miles@megapath.net>
Cc: <linux-kernel@vger.kernel.org>,
"Norberto Pellicci" <pellicci@home.com>, <Robert.Siemer@gmx.de>,
<Markus.Kuhn@cl.cam.ac.uk>
Subject: RE: 2.4.1 -- Unresolved symbols in radio-miropcm20.o
Date: Wed, 31 Jan 2001 17:22:32 +0100 [thread overview]
Message-ID: <NCBBIEBKAIAPGJDGPNCJOENCCFAA.R.A.Reitsma@wbmt.tudelft.nl> (raw)
In-Reply-To: <4987.980895146@ocs3.ocs-net>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
>-----Original Message-----
>From: Keith Owens [mailto:kaos@ocs.com.au]
>Sent: dinsdag 30 januari 2001 23:52
>To: Miles Lane
>Cc: linux-kernel@vger.kernel.org; Ruurd Reitsma; Norberto Pellicci
>Subject: Re: 2.4.1 -- Unresolved symbols in radio-miropcm20.o
>
>
>On Tue, 30 Jan 2001 13:08:12 -0800,
>Miles Lane <miles@megapath.net> wrote:
>>depmod: *** Unresolved symbols in
>>/lib/modules/2.4.1/kernel/drivers/media/radio/radio-miropcm20.o
>>depmod: aci_write_cmd
>>depmod: aci_indexed_cmd
>>depmod: aci_write_cmd_d
>
>Those symbols are defined in drivers/sound/aci.c but are not exported
>for other modules to use. The aci and miropcm20 code needs to be
>changed to support use as modules. Also the config.in files need
They are being exported, otherwise miropcm20.o won't work, would it? I've
just been too lazy to change the Config.in properly. It is however mentioned
in the radio-miropcm20 helpfile.
>fixing for these files, it is possible to select combinations of aci
>and miropcm20 that will fail to link (miropcm20 built in, aci not
>selected or selected as a module) or fail to load (miropcm20 selected
>as a module, aci not selected).
>
appearently Robert Siemer's patch didn't make it to the actual kernel. He
did change the config.in and made some changes to aci.c to support his
version of the firmware. He'll probably be happy to maintain the driver
since I threw out the pmc20 card.
--Ruurd
[-- Attachment #2: aci.patch.bz2 --]
[-- Type: application/octet-stream, Size: 5595 bytes --]
next prev parent reply other threads:[~2001-01-31 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 21:08 Miles Lane
2001-01-30 22:52 ` Keith Owens
2001-01-31 7:12 ` Miles Lane
2001-01-31 8:46 ` Arjan van de Ven
2001-01-31 8:48 ` Keith Owens
2001-01-31 10:55 ` Peter Samuelson
2001-01-31 11:07 ` Arjan van de Ven
[not found] ` <14967.62433.949844.559264@wire.cadcamlab.org>
2001-01-31 11:19 ` Arjan van de Ven
2001-01-31 11:48 ` Peter Samuelson
2001-01-31 16:22 ` Ruurd A. Reitsma [this message]
2001-02-01 15:50 ` Robert Siemer
2001-01-31 20:21 ` Robert Siemer
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=NCBBIEBKAIAPGJDGPNCJOENCCFAA.R.A.Reitsma@wbmt.tudelft.nl \
--to=r.a.reitsma@wbmt.tudelft.nl \
--cc=Markus.Kuhn@cl.cam.ac.uk \
--cc=Robert.Siemer@gmx.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapath.net \
--cc=pellicci@home.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 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®