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 15:07:43 -0500	[thread overview]
Message-ID: <3EB02D0F.1080101@cox.net> (raw)
In-Reply-To: <20030430090242.GA15480@codepoet.org>

Erik Andersen wrote:
> On Fri Apr 25, 2003 at 02:10:31PM +0200, Marc-Christian Petersen wrote:
> 
>>On Friday 25 April 2003 14:01, Marc-Christian Petersen wrote:
>>
>>Hi again,
>>
>>
>>>>I was crazy enough to take ALSA 0.9.2 and made it into a patch vs
>>>>2.4.x a week or two ago.  I just prefer to have ALSA be part of
>>>>the kernel rather than needing to compile it seperately all the
>>>>time.  The patch, along with various other things, is included as
>>>>part of my 2.4.21-rc1-erik kernel:
>>>
>>>Are you sure that this is 0.9.2 ALSA? I am afraid it is 0.9.0-rc6.
>>
>>this looks _very_ similar to the patch I had in WOLK4 some time ago and it was 
>>0.9.0-rc6.
> 
> 
> I finally got a bit of time this morning, so I have now updated
> my patch set.  I check very carefully and made sure I generated
> my ALSA 0.9.2 patch from the correct kernel tree this time, so 
> it actually contains my 0.9.2 port this time.
> 
>     http://codepoet.org/kernel/
> 
> Sorry about having the wrong alsa patch in there last time.  Last
> time around I has accidentlly built my alsa patch from my older
> alsa kernel tree.  I have this built into my kernel and I now see 
> 
>     Partition check:
>      hda: hda1 hda2
>     Advanced Linux Sound Architecture Driver Version 0.9.2.
>     PCI: Setting latency timer of device 00:11.5 to 64
>     ALSA device list:
>       #0: VIA 8233 at 0xcc00, irq 5
> 
> on bootup and xmms is playing.  Hope this is helpful,

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?
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.

Thanks,
David


  reply	other threads:[~2003-04-30 19:55 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 [this message]
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
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=3EB02D0F.1080101@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).