All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: CONFIG_SND_RTC and CONFIG_SND_RTCTIMER and CONFIG_RTC, oh my!
Date: Tue, 14 May 2002 10:49:22 +0200	[thread overview]
Message-ID: <3CE0CF92.F5CFFB38@ladisch.de> (raw)

I tried to use the RTC callback timer with my 2.4.12 kernel.
Patching the kernel went fine, but then ALSA wouldn't compile the
snd-rtctimer.o module, although configure said:
| checking for RTC callback support in kernel ... "yes"

A glance at alsa-kernel/core/Makefile shows that both CONFIG_RTC and
CONFIG_SND_RTCTIMER need to be defined:

	ifeq ($(subst m,y,$(CONFIG_RTC)),y)
	  obj-$(CONFIG_SND_RTCTIMER) += snd-timer.o
	  obj-$(CONFIG_SND_RTCTIMER) += snd-rtctimer.o
	endif

... but neither appears in alsa-driver/Makefile.conf, apparently
because configure thinks it should define CONFIG_SND_RTC instead:

alsa-driver/configure.in:
	...
	rtcsup="0"
	...
	  AC_MSG_RESULT("yes");rtcsup="m",
	  AC_MSG_RESULT("no");rtcsup="n",
	  AC_MSG_RESULT("unknown");rtcsup="n"
	...
	CONFIG_SND_RTC=$rtcsup
	AC_SUBST(CONFIG_SND_RTC)
	if test "$CONFIG_SND_RTC" = "1"; then
	  AC_DEFINE(CONFIG_SND_RTC)
	fi

Additionally, it's unclear whether the value of CONFIG_SND_RTC should
be 0/1 or n/m.


Sorry, no patch because I'm lacking the autoconf knowledge for this.
(I got it to compile (and run) by hacking the makefile, but I won't
submit _this_ change. :-)


Clemens

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

             reply	other threads:[~2002-05-14  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  8:49 Clemens Ladisch [this message]
2002-05-14 17:56 ` CONFIG_SND_RTC and CONFIG_SND_RTCTIMER and CONFIG_RTC, oh my! Takashi Iwai
2002-05-17 11:21 ` Clemens Ladisch
2002-05-17 15:25   ` 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=3CE0CF92.F5CFFB38@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    /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.