All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Adrian Knoth <adi@drcomp.erfurt.thur.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: RME MADIFX mainline inclusion
Date: Tue, 07 Apr 2015 12:03:19 +0200	[thread overview]
Message-ID: <s5hd23g9rx4.wl-tiwai@suse.de> (raw)
In-Reply-To: <5522B34B.3090404@drcomp.erfurt.thur.de>

At Mon, 06 Apr 2015 18:24:43 +0200,
Adrian Knoth wrote:
> 
> Hi Takashi!
> 
> Back in the days (late 2012 I guess), I wrote the MADIFX driver based on
> the existing RME hdspm.c.
> 
> I never had physical access to this 1399 Euro audio interface, only the
> OSX driver and a shell login to one of IOSONO's machines which
> temporarily featured such a card.
> 
> I know there are other users like University of Washington (DXARTS) and
> probably some more (the usual WFS suspects).
> 
> Long story short: I don't have such a card and since I no longer work in
> Linux audio, I guess I won't have access in the foreseeable future.
> 
> That said, I think the driver should be part of the mainline kernel, so
> it gets all the love the other drivers get (static code analysis, API
> changes etc.)
> 
> I think I've ported everything you guys have done to hdspm: I've read
> the commitlog for hdspm and applied those changes to the madifx driver.
> 
> Code is here:
> 
>     https://github.com/adiknoth/madifx/commits/tokernel
> 
> 
> Status:
> 
>   * PCM playback/capture working (SS and DS tested, QS untested)
>   * MIDI working
>   * All card settings working (e.g. TX64, SMUX, AESpro, WC-Term, 
> WC-singlespeed...)
>   * Slave Mode/External clock selection working
>   * Mirror-MADI1-to-Out2+3 maybe working (untested)
>   * Redundancy mode maybe working (untested)
>   * ioctls implemented (see ioctl.c)
>   * Static mixer working (fixed 1:1 mapping)
>   * DSP NOT working. RME doesn't intend to release any information 
> regarding the DSP.
>   * Adjustable mixer NOT working (needs new userspace tools)
>   * Levelmetering NOT working (maybe wrong, needs new userspace tools)
> 
> 
> I have no idea who could write the new mixer code. Apparently, demand is
> low, maybe zero.
> 
> checkpatch reports four warnings of which one is a false-positive, the
> other one doesn't make sense and only two are real but somewhat ugly to
> fix (line over 80 with really long array indices).
> 
> In its current state, can I send you three patches (Kconfig, madifx.h,
> madifx.c) that add said driver to sound/pci/rme9652?

Well, I really want some testers whether the merged code actually
works.  The code looks fine through a quick glance, so the only
requirement is the test (and the demands, of course).  If we can get
someone, then I'll happily merge the code after review.

Could you contact some people for testing?


thanks,

Takashi

  reply	other threads:[~2015-04-07 10:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 16:24 RME MADIFX mainline inclusion Adrian Knoth
2015-04-07 10:03 ` Takashi Iwai [this message]
2015-04-07 10:36   ` humbert.olivier.1
2015-04-07 11:05   ` Adrian Knoth
2015-04-07 11:28     ` IOhannes m zmoelnig
2015-04-07 11:48       ` Takashi Iwai
2015-04-17 20:56     ` Heikki Lindholm
2015-04-22 16:02     ` Markus Seeber
2015-08-08 16:23       ` [PATCH 0/4] Driver for RME MADI FX Adrian Knoth
2015-08-08 16:23         ` [PATCH 1/4] ALSA: madifx - Makefile entries " Adrian Knoth
2015-08-10  8:33           ` Takashi Iwai
2015-08-08 16:23         ` [PATCH 2/4] ALSA: Add RME MADI FX Kconfig entries Adrian Knoth
2015-08-10  8:35           ` Takashi Iwai
2015-08-08 16:23         ` [PATCH 3/4] ALSA: madifx - Expose preliminary userspace interface Adrian Knoth
2015-08-10  8:42           ` Takashi Iwai
2015-08-08 16:23         ` [PATCH 4/4] ALSA: madifx - Add support for RME MADI FX Adrian Knoth
2015-08-10  9:22           ` 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=s5hd23g9rx4.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=adi@drcomp.erfurt.thur.de \
    --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.