From: Takashi Iwai <tiwai@suse.de>
To: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
Cc: alsa-devel@lists.sourceforge.net,
"linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: [Alsa-devel] unresolved symbol udelay with ALSA on PPC
Date: Mon, 13 May 2002 11:38:42 +0200 [thread overview]
Message-ID: <s5hsn4w8k0t.wl@alsa2.suse.de> (raw)
In-Reply-To: <3CDF867F.44DA2DAD@folkwang-hochschule.de>
Hi Jörn,
At Mon, 13 May 2002 11:25:19 +0200,
Jörn Nettingsmeier wrote:
>
> hi !
>
> sorry for crossposting, this one is probably inappropriate for either
> the alsa or the ppc list. the problem is, i don't know which ;)
>
> this is after successfully compiling 2.4.19-pre8-ben0 for PPC on a
> powerbook g3 (pismo) and installing the alsa drivers from
> alsa-driver-0.9.0rc1.tar.bz2:
>
> ephraim:/usr/src/alsa-driver-0.9.0rc1 # depmod -ae -F
> /boot/System.map-2.4.19-pre8-ben0
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19-pre8-ben0/kernel/sound/ppc/snd-powermac.o
> depmod: udelay
>
> can anyone clue me in on this ? i grepped for udelay, but it seems it's
> a very popular string in the source tree, so i gave up :( it seems to be
> defined alright for other kernel modules. afaics, snd-powermac is the
> only one that has problems.
i hope it was fixed on cvs now.
(as always, it's due to missing include..)
could you try to update?
anyway, i'll spend some time to debug powermac drivers in this week.
there have been bug reports regarding awacs/screamer chips.
the tumbler chip was fixed in the last week.
now it supports bass/treble and DRC, and the volume changes more
reasonably.
Takashi
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-13 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 9:25 unresolved symbol udelay with ALSA on PPC Jörn Nettingsmeier
2002-05-13 9:34 ` [Alsa-devel] " Jaroslav Kysela
2002-05-13 9:38 ` Takashi Iwai [this message]
2002-05-13 9:58 ` Jörn Nettingsmeier
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=s5hsn4w8k0t.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nettings@folkwang-hochschule.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).