From: Brad Figg <brad.figg@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/1] Daily snapshot not building on 2.6.32
Date: Thu, 24 Jun 2010 11:47:56 -0700 [thread overview]
Message-ID: <4C23A85C.5090109@canonical.com> (raw)
In-Reply-To: <s5hfx0cclv4.wl%tiwai@suse.de>
On 06/24/2010 11:43 AM, Takashi Iwai wrote:
> At Thu, 24 Jun 2010 11:07:27 -0700,
> Brad Figg wrote:
>>
>> On 06/24/2010 08:40 AM, Takashi Iwai wrote:
>>> At Thu, 24 Jun 2010 08:37:40 -0700,
>>> Brad Figg wrote:
>>>>
>>>> On 06/24/2010 08:35 AM, Takashi Iwai wrote:
>>>>> At Thu, 24 Jun 2010 08:27:37 -0700,
>>>>> Brad Figg wrote:
>>>>>>
>>>>>> On 06/24/2010 08:02 AM, Takashi Iwai wrote:
>>>>>>> At Thu, 24 Jun 2010 07:56:35 -0700,
>>>>>>> Brad Figg wrote:
>>>>>>>>
>>>>>>>> On 06/23/2010 11:27 PM, Takashi Iwai wrote:
>>>>>>>>> At Wed, 23 Jun 2010 11:37:16 -0700,
>>>>>>>>> Brad Figg wrote:
>>>>>>>>>>
>>>>>>>>>> I've had to apply the following patch to successfully build
>>>>>>>>>> the daily snapshot on 2.6.32. Without this patch I get:
>>>>>>>>>
>>>>>>>>> Which tarball? The latest one works fine for me.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Takashi
>>>>>>>>
>>>>>>>> Today's snapshot is giving me the exact same error.
>>>>>>>
>>>>>>> Did you get from the URL below, right?
>>>>>>>
>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>>>>>>>
>>>>>>> Then check config.log whether usb_alloc_coherent() check worked.
>>>>>>>
>>>>>>>
>>>>>>> Takashi
>>>>>>>
>>>>>>
>>>>>> I'm pulling the snapshot from the correct location. However:
>>>>>> checking usb_alloc_coherent... no
>>>>>
>>>>> That's correct. Then it must have
>>>>> #undef CONFIG_SND_HAVE_USB_ALLOC_COHERENT
>>>>> in include/config.h, and incldue/adriver.h should define a wrapper for
>>>>> the function. Please check it.
>>>>>
>>>>>
>>>>> Takashi
>>>>
>>>> include/config.h:
>>>>
>>>> /* #undef CONFIG_SND_HAVE_USB_ALLOC_COHERENT */
>>>>
>>>>
>>>>
>>>> include/adriver.h:
>>>>
>>>> #ifndef CONFIG_SND_HAVE_USB_ALLOC_COHERENT
>>>> #define usb_alloc_coherent usb_buffer_alloc
>>>> #define usb_free_coherent usb_buffer_free
>>>> #endif
>>>
>>> Check whether the code patch there reaches while compiling ua101.c.
>>>
>>>
>>> Takashi
>>
>> And, by the way, I'm getting this error when trying to build today's snapshot
>> on 2.6.35.
>>
>> CC [M] /home/work/alsa/alsa-driver/acore/pcm_native.o
>> /home/work/alsa/alsa-driver/acore/pcm_native.c: In function ‘snd_pcm_hw_params’:
>> /home/work/alsa/alsa-driver/acore/pcm_native.c:468: error: implicit declaration of function ‘pm_qos_remove_requirement’
>> /home/work/alsa/alsa-driver/acore/pcm_native.c:471: error: implicit declaration of function ‘pm_qos_add_requirement’
>> make[3]: *** [/home/work/alsa/alsa-driver/acore/pcm_native.o] Error 1
>> make[2]: *** [/home/work/alsa/alsa-driver/acore] Error 2
>> make[1]: *** [_module_/home/work/alsa/alsa-driver] Error 2
>>
>> Which I've not been able to figure out any work around after an hour or
>> more of working on it.
>
> Likely the pm-qos API was changed once again.
> In general, the latest kernel is not targeted for alsa-driver external
> builds. Use sound git tree instead.
>
> I'll fix it after I back from my vacation (about a week).
>
>
> thanks,
>
> Takashi
Thanks.
--
Brad Figg brad.figg@canonical.com http://www.canonical.com
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2010-06-24 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 18:37 [PATCH 1/1] Daily snapshot not building on 2.6.32 Brad Figg
2010-06-24 6:27 ` Takashi Iwai
2010-06-24 14:56 ` Brad Figg
2010-06-24 15:02 ` Takashi Iwai
2010-06-24 15:27 ` Brad Figg
2010-06-24 15:35 ` Takashi Iwai
2010-06-24 15:37 ` Brad Figg
2010-06-24 15:40 ` Takashi Iwai
2010-06-24 15:50 ` Brad Figg
2010-06-24 18:42 ` Takashi Iwai
2010-06-24 18:07 ` Brad Figg
2010-06-24 18:43 ` Takashi Iwai
2010-06-24 18:47 ` Brad Figg [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=4C23A85C.5090109@canonical.com \
--to=brad.figg@canonical.com \
--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 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.