From: Takashi Iwai <tiwai@suse.de>
To: andi@rhlx01.fht-esslingen.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: snd-azt3328 bug.
Date: Thu, 28 Nov 2002 16:34:33 +0100 [thread overview]
Message-ID: <s5hy97dzp12.wl@alsa2.suse.de> (raw)
In-Reply-To: <20021126214335.GA4601@rhlx01.fht-esslingen.de>
At Tue, 26 Nov 2002 22:43:35 +0100,
Andreas Mohr wrote:
>
> On Mon, Nov 25, 2002 at 09:37:03AM -0800, alsa-devel-request@lists.sourceforge.net wrote:
> > Message: 3
> > Date: Mon, 25 Nov 2002 11:40:38 +0900
> > From: Patrick Shirkey <pshirkey@boosthardware.com>
> > Organization: Boost Hardware
> > To: alsa-devel@lists.sourceforge.net, lzshun@163.com
> > Subject: [Alsa-devel] snd-azt3328 bug.
> >
> > This is a multi-part message in MIME format.
> > --------------000909080605060505030706
> > Content-Type: text/plain; charset=us-ascii; format=flowed
> > Content-Transfer-Encoding: 7bit
> >
> > I have forwarded this on to hte alsa-devel list as this is a bug. Please
> > sign up to the alsa-devel mailing list to help get this driver working
> > correctly.
> >
> > ----
> > i do it by
> > http://alsa-project.org/alsa-doc/doc-php/template.php3?company=AzTech&card=PCI+168&chip=AZF3328&module=azt3328
> > why i use alsa-0.9.0rc6 driver and
> > when run to
> >
> > [root@localhost root]# modprobe snd-azt3328
> > /lib/modules/2.4.18-14/kernel/sound/pci/snd-azt3328.o: unresolved symbol
> > snd_mpu401_uart_interrupt_R4ea4dc60
> > /lib/modules/2.4.18-14/kernel/sound/pci/snd-azt3328.o: unresolved symbol
> > snd_mpu401_uart_new_R0588a8ba
> > /lib/modules/2.4.18-14/kernel/sound/pci/snd-azt3328.o: insmod
> > /lib/modules/2.4.18-14/kernel/sound/pci/snd-azt3328.o failed
> > /lib/modules/2.4.18-14/kernel/sound/pci/snd-azt3328.o: insmod
> > snd-azt3328 failed
> > ----
> Hmm, I'm not so sure about that.
>
> While I had the same problems with my driver (err, yep, I'm the author ;),
> recompiling the kernel and reinstalling ALSA modules helped.
> However as another user had the same problem and this now turns up on
> alsa-devel with *my* driver mentioned (I'm sure there are at least
> 2.73 Linux users in the whole world owning this card ;-), I'm willing
> to believe that maybe it's not simply a general module versioning problem,
> but maybe rather a module handling problem of my driver.
i guess he compiled with --with-cards=azt3328.
there was a dependency bug in alsa-driver tree and mpu401_uart.o was
not compiled if only azt3328 driver is specified.
now fixed on cvs.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
prev parent reply other threads:[~2002-11-28 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18GNBK-0004xN-00@sc8-sf-list2.sourceforge.net>
2002-11-26 21:43 ` snd-azt3328 bug Andreas Mohr
2002-11-28 15:34 ` Takashi Iwai [this message]
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=s5hy97dzp12.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andi@rhlx01.fht-esslingen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.