From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: patch@alsa-project.org
Cc: Adrian Knoth <adi@drcomp.erfurt.thur.de>, alsa-devel@alsa-project.org
Subject: [PATCH RFC 0/4] Driver for RME MADI FX
Date: Fri, 1 Feb 2013 13:48:37 +0100 [thread overview]
Message-ID: <1359722921-18769-1-git-send-email-adi@drcomp.erfurt.thur.de> (raw)
Hi!
I've been developing an out-of-tree driver for the RME MADI FX. History
is available at
https://github.com/adiknoth/madifx
but doesn't follow any kernel convention regarding commit isolation, it
was basically a backup/scratchpad during development.
I don't have too much feedback, yet, but I guess it makes sense to
mainline it earlier than later, increase the driver's exposure and fix
any problems when the card is in more widespread use.
Note that this patch series is essentially RFC right now to gather
developer feedback.
Cheers
Adrian Knoth (4):
ALSA: madifx - Makefile entries for RME MADI FX
ALSA: Add RME MADI FX Kconfig entries
ALSA: madifx - Expose preliminary userspace interface
ALSA: madifx - Add support for RME MADI FX
include/uapi/sound/madifx.h | 173 ++
sound/pci/Kconfig | 21 +
sound/pci/rme9652/Makefile | 2 +
sound/pci/rme9652/madifx.c | 3986 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 4182 insertions(+)
create mode 100644 include/uapi/sound/madifx.h
create mode 100644 sound/pci/rme9652/madifx.c
--
1.7.10.4
next reply other threads:[~2013-02-01 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 12:48 Adrian Knoth [this message]
2013-02-01 12:48 ` [PATCH RFC 1/4] ALSA: madifx - Makefile entries for RME MADI FX Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 2/4] ALSA: Add RME MADI FX Kconfig entries Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 3/4] ALSA: madifx - Expose preliminary userspace interface Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 4/4] ALSA: madifx - Add support for RME MADI FX Adrian Knoth
2013-02-02 15:16 ` [PATCH RFC 2/4] ALSA: Add RME MADI FX Kconfig entries Andre Schramm
2013-02-03 11:52 ` Adrian Knoth
2013-02-04 16:24 ` Adrian Knoth
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=1359722921-18769-1-git-send-email-adi@drcomp.erfurt.thur.de \
--to=adi@drcomp.erfurt.thur.de \
--cc=alsa-devel@alsa-project.org \
--cc=patch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).