From: Tim Blechmann <tim@klingt.org>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: alsa driver for digigram lx6464es
Date: Sun, 22 Mar 2009 20:34:08 +0100 [thread overview]
Message-ID: <49C692B0.7040609@klingt.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 766 bytes --]
hi all,
i have implemented the prototype of an alsa driver for the digigram
lx6464es audio interface. audio i/o is basically working, although not
very well tested, yet. the driver is available from my git repository [1].
features:
- i/o support for 64 channels via ethersound [2]
missing features:
- handling of xrun notification
- configuration of the ethersound network needs to be done externally
takashi, i would like to submit the patch to alsa soon ... how should i
proceed? can you do a review of the code?
thanks, tim
[1]
http://tim.klingt.org/git?p=digigram.git;a=shortlog;h=refs/heads/lx6464es
[2] http://www.ethersound.com/
--
tim@klingt.org
http://tim.klingt.org
I don't write music for sissy ears.
Charles Ives
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2009-03-22 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 19:34 Tim Blechmann [this message]
2009-03-23 6:53 ` alsa driver for digigram lx6464es Takashi Iwai
2009-03-23 10:12 ` [PATCH] alsa: lx6464es - driver for the digigram lx6464es interface Tim Blechmann
2009-03-23 10:44 ` Takashi Iwai
2009-03-24 11:23 ` Tim Blechmann
2009-03-24 11:24 ` [PATCH v2] " Tim Blechmann
2009-03-25 11:11 ` Takashi Iwai
2009-03-25 13:56 ` Tim Blechmann
2009-04-14 12:18 ` Takashi Iwai
2009-03-23 10:26 ` alsa driver for digigram lx6464es Tim Blechmann
2009-03-23 10:49 ` Takashi Iwai
2009-03-23 11:04 ` Tim Blechmann
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=49C692B0.7040609@klingt.org \
--to=tim@klingt.org \
--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.