From: Takashi Iwai <tiwai@suse.de>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: NULL pointer dereference in ALSA triggered through saa7134-alsa
Date: Mon, 10 Aug 2009 16:00:14 +0200 [thread overview]
Message-ID: <s5hab27n501.wl%tiwai@suse.de> (raw)
In-Reply-To: <4A8025BF.7030404@pardus.org.tr>
At Mon, 10 Aug 2009 16:50:55 +0300,
Ozan Çağlayan wrote:
>
> Hi,
>
> I've finally succesfully compiled and linked saa7134-alsa driver using
> an external alsa-driver and its Module.symvers file. Everything seems
> okay, no undefined symbol or something else:
>
> - An installed 2.6.30.4 kernel which only builds and brings soundcore
> and sound_firmware,
> - Latest alsa-driver built externally and installed,
> - Latest saa7134-alsa, cx88-alsa, etc. code from linus-2.6 (seen that
> they don't affected by some API/ABI changes) patched on top of the
> alsa-driver tarball,
The external drivers using ALSA API have to be built with the
newer ALSA header files from alsa-driver tree. It's not enough to
change snd_card_new() with snd_card_create(). The core structure
was changed, so the whole build has to be adjusted, too.
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-08-10 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 13:50 NULL pointer dereference in ALSA triggered through saa7134-alsa Ozan Çağlayan
2009-08-10 14:00 ` Takashi Iwai [this message]
2009-08-10 15:42 ` Ozan Çağlayan
2009-08-10 15:50 ` [alsa-devel] " Takashi Iwai
2009-08-10 16:06 ` Ozan Çağlayan
2009-08-10 16:11 ` [alsa-devel] " Takashi Iwai
2009-08-10 18:28 ` Ozan Çağlayan
2009-08-10 19:08 ` Ozan Çağlayan
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=s5hab27n501.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-media@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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