From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: [alsa-devel] NULL pointer dereference in ALSA triggered through saa7134-alsa
Date: Mon, 10 Aug 2009 18:42:20 +0300 [thread overview]
Message-ID: <4A803FDC.8070005@pardus.org.tr> (raw)
In-Reply-To: <s5hab27n501.wl%tiwai@suse.de>
Takashi Iwai wrote:
> 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.
>
Actually that was the 0th step that I forgot to mention. I'm installing
the headers from the alsa-driver snapshot into /usr/include/sound and
then I build alsa-driver. Then I use the symvers from the alsa-driver
build alltogether with the headers that I've already installed into
/usr/include/sound to build the V4L ones.
Sorry If I understand what you said wrongly.
Thanks,
next prev parent reply other threads:[~2009-08-10 15:42 UTC|newest]
Thread overview: 6+ 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 ` [alsa-devel] " Takashi Iwai
2009-08-10 15:42 ` Ozan Çağlayan [this message]
2009-08-10 15:50 ` Takashi Iwai
2009-08-10 16:06 ` Ozan Çağlayan
2009-08-10 16:11 ` Takashi Iwai
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=4A803FDC.8070005@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=alsa-devel@alsa-project.org \
--cc=linux-media@vger.kernel.org \
--cc=tiwai@suse.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