From: Perry Gilfillan <perrye@linuxmail.org>
To: alsa-list <alsa-devel@lists.sourceforge.net>
Subject: Adding module to ALSA tree with Kconfig script
Date: Mon, 26 Apr 2004 09:54:44 -0500 [thread overview]
Message-ID: <408D22B4.9040106@linuxmail.org> (raw)
Hello,
It seems that between alsa-driver-1.0.2 and 1.0.4, the
scripts/Modules.dep file has been dropped in favour of Kconfig scripts.
This seems like a good thing, but I'm at a loss to get my snd-tvmixer
to work by this method.
I've looked at the revised "Writing an ALSA Driver" chapter 14, and
still can't get it straight. The first hurdle is creating a Kconfig
script in the alsa-kernel/i2c directory. This is what I came up with:
# ALSA I2C drivers
menu "I2C devices"
depends on SND!=n && I2C
config SND_TVMIXER
tristate "Video 4 Linux TV-Mixer"
depends on SND
help
Say 'Y' or 'M' to include support for TV-Mixer.
This module requires that the V4L msp3400 module be
present.
endmenu
Then I have added these lines to alsa-kernel/i2c/Makefile:
snd-tvmixer-objs := tvmixer.o
obj-$(CONFIG_SND_TVMIXER) += snd-tvmixer.o
Chapter 14 has the second line written as 'extra-obj-$( ....', so I
tried it both ways.
I'm building against a 2.4.25 kernel, so how do I invoke the Kconfig
scripts? or do I need to RTFine kbuild Manual?
Thanks,
Perry
-----
Gilfillan Family: http://www.gilfillan.org/
Projects:
V3TV: http://www.gilfillan.org/v3tv/
VPX3224: http://www.gilfillan.org/vpx3224/
snd-tvmixer: http://www.gilfillan.org/ALSA/
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
next reply other threads:[~2004-04-26 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 14:54 Perry Gilfillan [this message]
2004-04-26 17:00 ` Adding module to ALSA tree with Kconfig script 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=408D22B4.9040106@linuxmail.org \
--to=perrye@linuxmail.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.