From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: NULL pointer dereference in ALSA triggered through saa7134-alsa
Date: Mon, 10 Aug 2009 21:28:35 +0300 [thread overview]
Message-ID: <4A8066D3.7050107@pardus.org.tr> (raw)
In-Reply-To: <s5hljlrlkcf.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Mon, 10 Aug 2009 19:06:29 +0300,
> Ozan Çağlayan wrote:
>
>> Takashi Iwai wrote:
>>
>>> But /usr/include/sound isn't used for building kernel modules normally.
>>> Unless any hack is added, these files have to be installed to the
>>> kernel header directory.
>>>
>>>
>> Ah you're right, I totally missed that one. Thanks, will try to
>> workaround that.
>>
>
> Well, the best would be to make alsa-driver backward compatible.
> Basically we need to patch headers in alsa-kernel tree to be
> binary-compatible with older versions, i.e. adjusting the fields
> in struct snd_pcm or so, and supply the compatible function,
> snd_card_new() in addition.
>
The diff between 2.6.30.4 sound headers and current snapshot was
relatively small (700~ lines), snd_card_new() is removed, a lot of SoC
stuff was modified, etc. I patched those into my kernel headers and then
built the drivers but still the same issue. I'm now compiling 2.6.30.4
with ALSA and V4L drivers to see if I have that Oops with vanilla modules.
Regards,
_______________________________________________
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 18:28 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
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 [this message]
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=4A8066D3.7050107@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=alsa-devel@alsa-project.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