From: Clemens Ladisch <clemens@ladisch.de>
To: o-takashi@sakamocchi.jp
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
linux1394-devel@lists.sourceforge.net, ffado-devel@lists.sf.net,
perex@perex.cz
Subject: Re: [PATCH 8/8] modify Makefile and Kconfig to build this module
Date: Mon, 03 Jun 2013 13:19:00 +0200 [thread overview]
Message-ID: <51AC7BA4.4020804@ladisch.de> (raw)
In-Reply-To: <1370102158-24389-9-git-send-email-o-takashi@sakamocchi.jp>
o-takashi@sakamocchi.jp wrote:
> +config SND_FIREWORKS
> + tristate "Echo Fireworks chipset support"
> + select SND_PCM
> + select SND_RAWMIDI
> + select SND_FIREWIRE_LIB
> + help
> + Say Y here to include support for FireWire devices based
> + on Echo Digital Audio's Fireworks architecture:
> + * Echo AudioFire 2/4/8/8a/Pre8/12
> + * Echo Fireworks 8/HDMI
> + * Gibson Goldtop/RIP
> + * Mackie Onyx 400F/1200F
> +
> + To compile this driver as a module, choose M here: the module
> + will be called snd-fireworks.
We'll have to find some mechanism to prevent FFADO from blowing up just
because a distribution update has introduced this driver.
Regards,
Clemens
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
next prev parent reply other threads:[~2013-06-03 11:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 15:55 [PATCH 0/8] [RFC] new driver for Echo Audio's Fireworks based devices o-takashi
2013-06-01 15:55 ` [PATCH 1/8] add main file of driver module o-takashi
2013-06-03 11:18 ` Clemens Ladisch
2013-06-01 15:55 ` [PATCH 2/8] add device specific command o-takashi
2013-06-03 11:18 ` Clemens Ladisch
2013-06-06 17:33 ` Takashi Sakamoto
2013-06-06 22:49 ` Takashi Sakamoto
2013-06-01 15:55 ` [PATCH 3/8] add control interfaces o-takashi
2013-06-01 15:55 ` [PATCH 4/8] add handling AMDTP stream o-takashi
2013-06-01 15:55 ` [PATCH 5/8] add MIDI interface o-takashi
2013-06-03 11:18 ` Clemens Ladisch
2013-06-01 15:55 ` [PATCH 6/8] add PCM interface o-takashi
2013-06-03 11:18 ` Clemens Ladisch
2013-06-01 15:55 ` [PATCH 7/8] add proc interface o-takashi
2013-06-01 15:55 ` [PATCH 8/8] modify Makefile and Kconfig to build this module o-takashi
2013-06-03 11:19 ` Clemens Ladisch [this message]
2013-06-03 11:18 ` [PATCH 0/8] [RFC] new driver for Echo Audio's Fireworks based devices Clemens Ladisch
2013-06-07 12:16 ` Takashi Sakamoto
2013-06-08 9:29 ` Clemens Ladisch
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=51AC7BA4.4020804@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=ffado-devel@lists.sf.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--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