linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David van Hoose <davidvh@cox.net>
To: andersen@codepoet.org
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALSA and 2.4.x
Date: Wed, 30 Apr 2003 19:09:24 -0500	[thread overview]
Message-ID: <3EB065B4.6050309@cox.net> (raw)
In-Reply-To: <20030430205021.GA20614@codepoet.org>

Erik Andersen wrote:
> On Wed Apr 30, 2003 at 03:07:43PM -0500, David van Hoose wrote:
> 
>>I'm getting an unresolved in soundcore.o that is preventing me from 
>>having sound.
>>/lib/modules/2.4.21-rc1/kernel/sound/soundcore.o: unresolved symbol 
>>devfs_remove
>>/lib/modules/2.4.21-rc1/kernel/sound/soundcore.o: insmod 
>>/lib/modules/2.4.21-rc1/kernel/sound/soundcore.o failed
>>/lib/modules/2.4.21-rc1/kernel/sound/soundcore.o: insmod snd-card-0 failed
>>
>>Can that be fixed?
> 
> 
> It looks like this is simply a minor include file problem.
> sound/sound_core.c needs 
>     #include <sound/driver.h>
> added to it which should hopefully make this problem go away.
> 
> 
>>Also I have problems if I compile USB Audio and USB MIDI from the USB 
>>section AND USB Audio and USB MIDI from the ALSA section. Compilation 
>>fails in that situation. Might want to put the former patch up if this 
>>stuff might take a while to fix.
> 
> 
> This looked trivial enough to fix, I went ahead and
> regenerated my patch with these changes,

Got it. I patched sound_core.c and I have sound now. I'm assuming that 
was the only file that needed to be patched. Correct? Also, should the 
OSS soundcore option in menuconfig always be 'Y'? It seems to not want 
to be anything else.

I get this warning on almost every file during the compile.
In file included from /usr/src/linux-2.4.21-rc1/include/sound/driver.h:43,
                   from hwdep.c:22:
/usr/src/linux-2.4.21-rc1/include/sound/adriver.h:320:1: warning:
"vmalloc_to_page" redefined
In file included from
/usr/src/linux-2.4.21-rc1/include/linux/modversions.h:185,
from <command line>:1:
/usr/src/linux-2.4.21-rc1/include/linux/modules/ksyms.ver:66:1: warning:
this is the location of the previous definition

Another trivial patch perhaps?

Thanks for the patch!
David


  reply	other threads:[~2003-04-30 23:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 21:25 ALSA and 2.4.x Erik Andersen
2003-04-25  3:40 ` David van Hoose
2003-04-25 12:01 ` Marc-Christian Petersen
2003-04-25 12:10   ` Marc-Christian Petersen
2003-04-30  9:02     ` Erik Andersen
2003-04-30 20:07       ` David van Hoose
2003-04-30 20:22         ` Erik Andersen
2003-04-30 20:36           ` Willy Tarreau
2003-04-30 20:50         ` Erik Andersen
2003-05-01  0:09           ` David van Hoose [this message]
2003-04-25 12:24   ` Erik Andersen
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 13:35 David van Hoose
2003-04-24 13:43 ` Marc-Christian Petersen
2003-04-24 13:56   ` Maciej Soltysiak
2003-04-24 13:49 ` Con Kolivas

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=3EB065B4.6050309@cox.net \
    --to=davidvh@cox.net \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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;
as well as URLs for NNTP newsgroup(s).