From: James Pearson <james-p@moving-picture.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: 1.0.16rc1 release
Date: Tue, 22 Jan 2008 17:15:18 +0000 [thread overview]
Message-ID: <479624A6.7040700@moving-picture.com> (raw)
In-Reply-To: <s5h4pd5954z.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 22 Jan 2008 16:23:28 +0000,
> James Pearson wrote:
>>
>>It looks like alsa-driver-1.0.16rc1/acore/ioctl32/hwdep32_new.c should
>>be including "adriver.h" not "driver.h" ??
>
>
> Yes, it's a typo.
>
>
>>Also, at MODPOST stage:
>>
>>*** Warning: "mutex_destroy"
>>[/tmp/alsa-driver-1.0.16rc1/pci/oxygen/snd-oxygen-lib.ko] undefined!
>
>
> Do you have alsa-driver*/include/mutex.h?
There is no alsa-driver*/include/mutex.h, there is a
include/linux/mutex.h as part of the kernel - which contains:
/*
* Copyright (c) 2006 Cisco Systems. All rights reserved.
*
* This file is released under the GPLv2.
*/
/* mutex compatibility for pre-2.6.16 kernels */
#ifndef __LINUX_MUTEX_H
#define __LINUX_MUTEX_H
#include <asm/semaphore.h>
#define mutex semaphore
#define DEFINE_MUTEX(foo) DECLARE_MUTEX(foo)
#define mutex_init(foo) init_MUTEX(foo)
#define mutex_lock(foo) down(foo)
#define mutex_lock_interruptible(foo) down_interruptible(foo)
/* this function follows the spin_trylock() convention, so *
* it is negated to the down_trylock() return values! Be careful */
#define mutex_trylock(foo) !down_trylock(foo)
#define mutex_unlock(foo) up(foo)
#endif /* __LINUX_MUTEX_H */
i.e. it doesn't define mutex_destroy()
> Or, RH has an uncomplete mutex implementation?
Don't know - see above?
>>*** Warning: "do_posix_clock_monotonic_gettime"
>>[/tmp/alsa-driver-1.0.16rc1/acore/snd-timer.ko] undefined!
>>*** Warning: "do_posix_clock_monotonic_gettime"
>>[/tmp/alsa-driver-1.0.16rc1/acore/snd-pcm.ko] undefined!
>>
>>I'm not sure why its complaining about do_posix_clock_monotonic_gettime,
>>as this is there in the 2.6.9 RHEL4 kernel.
>
>
> It seems that the function isn't exported.
>
> The fix patch is below. Give it a try.
Patch fixed these issues
Thanks
James Pearson
next prev parent reply other threads:[~2008-01-22 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 11:49 1.0.16rc1 release Jaroslav Kysela
2008-01-22 16:23 ` James Pearson
2008-01-22 16:50 ` Takashi Iwai
2008-01-22 17:15 ` James Pearson [this message]
2008-01-22 17:20 ` Takashi Iwai
2008-01-22 17:39 ` James Pearson
2008-01-22 17:56 ` Tobin Davis
2008-01-22 19:25 ` 1.0.16rc1 release -- error: ‘system_utsname’ undeclared Rick Measham
2008-01-23 7:03 ` Takashi Iwai
2008-01-23 7:31 ` Takashi Iwai
2008-01-24 12:14 ` Rick Measham
2008-01-24 13:24 ` Takashi Iwai
2008-01-24 21:12 ` 1.0.16rc1 release -- error: 'system_utsname' undeclared Rick Measham
2008-01-25 8:03 ` Takashi Iwai
[not found] ` <4799CC9B.9050809@measham.id.au>
2008-01-25 12:10 ` Takashi Iwai
2008-01-25 13:33 ` Rick Measham
2008-01-25 13:48 ` Takashi Iwai
2008-01-25 13:51 ` Rick Measham
2008-01-25 14:19 ` 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=479624A6.7040700@moving-picture.com \
--to=james-p@moving-picture.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.