From: Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de>
To: alsa-devel@alsa-project.org
Cc: alsa-user@lists.sourceforge.net
Subject: Again: Alsa Driver Scarlett
Date: Wed, 17 Dec 2014 12:49:20 +0100 [thread overview]
Message-ID: <20141217114920.GA3288@x1-orm> (raw)
Hi,
this is relating to my post from September: There doesn't seem to be
any progress concerning the integration of the Scarlett alsa-driver
patch into Alsa.
Can someone on the list tell me how to invoke a process to get it
integrated?
The patch sources are here:
https://github.com/smilingthax/alsa-driver_scarlett
At the moment most of our students regularly have to reapply the patch
as soon as they upgrade their systems and it's pretty time consuming
and painful for the studio technicians and me to guide them through
the process of patching kernel modules, so it would be great to
simplify this process by integrating it into the official alsa
distribution. I can confirm that the patch still works well on our
systems.
--
Orm
------------------------------------------------------------------
Prof. Orm Finnendahl
Komposition
Hochschule für Musik und Darstellende Kunst
Eschersheimer Landstr. 29-39
60322 Frankfurt am Main
----- Forwarded message from Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de> -----
Subject: Re: [alsa-devel] Alsa Driver Scarlett
From: Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de>
To: alsa-devel@alsa-project.org
Date: Tue, 16 Sep 2014 15:49:25 +0200
Am Dienstag, den 16. September 2014 um 15:22:27 Uhr (+0200) schrieb Johannes Kroll:
>
> I guess I'll need to find the time to port the patch to a recent kernel
> when I upgrade, unless someone else does it first.
The patch still works on our recent kernels (we are on debian testing
with a 3.14-2 kernel), atm there is no porting necessary. I can also
confirm that the driver has no known issues on our systems (we use a
couple of Scarlett 18i20 in different configurations). It would be
great, though if the patch could get integrated into alsa. At the
moment it is quite painful for our students with linux laptops as they
have to reapply the patch on every upgrade.
--
Orm Finnendahl
------------------------------------------------------------------
Prof. Orm Finnendahl
Komposition
Hochschule für Musik und Darstellende Kunst
Eschersheimer Landstr. 29-39
60322 Frankfurt am Main
----- End forwarded message -----
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2014-12-17 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 11:49 Orm Finnendahl [this message]
2014-12-17 13:59 ` Again: Alsa Driver Scarlett 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=20141217114920.GA3288@x1-orm \
--to=orm.finnendahl@selma.hfmdk-frankfurt.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
/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.