All of lore.kernel.org
 help / color / mirror / Atom feed
From: forevernoob@tutanota.com
To: Alsa Devel <alsa-devel@alsa-project.org>
Subject: How trivial would it be to port the DICE driver from FFADO?
Date: Tue, 9 Aug 2022 16:44:23 +0200 (CEST)	[thread overview]
Message-ID: <N9213zQ--3-2@tutanota.com> (raw)

Hello,

I'm new to these kinds of mailing lists so please forgive me if I'm doing something dumb.

I would love to see Allen & Heath Zed R16 as well as Midas Venice F32 support in ALSA.

Currently (at least according to libffado-2.4.4/configuration), they are supported via the DICE driver:

{ # Allen and Heath Zed R16.  Information from Brendan Pike.
    vendorid    = 0x000004C4;
    modelid     = 0x00000000;
    vendorname  = "Allen and Heath";
    modelname   = "Zed R16";
    driver      = "DICE";
    mixer       = "Generic_Dice_EAP";
},
{ # Midas Venice F32.  Information from Jano Svitok.
    vendorid    = 0x0010C73F;
    modelid     = 0x00000001;
    vendorname  = "Midas";
    modelname   = "Venice F32";
    driver      = "DICE";
    mixer       = "Generic_Dice_EAP";
},

In their source code I think it's this file: http://subversion.ffado.org/browser/branches/2.4.x/libffado/src/dice/dice_eap.cpp

So my question would be: How difficult would it be to port this driver (more specifically: Port it sufficiently enough to support the aforementioned devices) ?

Are we talking trivial enough for someone with minimal C experience, a dedicated team of ALSA devs or something else?

Thanks in advance,
FN

             reply	other threads:[~2022-08-09 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 14:44 forevernoob [this message]
2022-08-10  0:32 ` How trivial would it be to port the DICE driver from FFADO? Takashi Sakamoto
2022-08-19  1:30 ` Takashi Sakamoto

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=N9213zQ--3-2@tutanota.com \
    --to=forevernoob@tutanota.com \
    --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.