From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Lee Revell <rlrevell@joe-job.com>,
James Courtier-Dutton <James@superbug.co.uk>,
Veli-Matti Valtonen <maligor@gmail.com>,
Ctirad Fertr <c.fertr@gmail.com>, Pavel Hofman <dustin@seznam.cz>,
michael@gernoth.net, Maxim Kachur <mcdebugger@duganet.ru>,
shane-alsa@cm.nu, Thomas Zehetbauer <thomasz@hostmaster.org>,
Alexander Samad <alex@samad.com.au>
Subject: [PATCH 0/130+] ALSA: emu10k1 & more
Date: Thu, 16 Feb 2023 12:33:05 +0100 [thread overview]
Message-ID: <Y+4UcetSxH6lDPoy@ugly> (raw)
moin,
i got myself an old e-mu 0404 card, because i found the analog hardware
well hackable for dc operation.
then i found the driver to be lacking, and got hacking that, too. hence
this blast from the past.
this is a huge branch with many internal dependencies, so i'm assuming
i'm not supposed to post a patch series.
instead it's on https://github.com/ossilator/linux/tree/ossis-alsa - let
me know if another review platform is preferable.
apart from the actual driver work, this contains some alsa patches
unrelated to emu10k1, some patches which really shouldn't be merged via
the alsa route (if at all), and some patches which are just collections
of questions (to which i hope to receive answers on github). this is of
course meant to be cleaned up in due time.
feel free to cherry-pick the patches you deem ready; i'll happily rebase
the branch.
some of these patches are not (fully) tested due to lack of hardware. in
particular, someone should check that SB Live! and Audigy cards still
work. then there is a whole bunch of e-mu card specific functionality
which targets the "bigger members of the family". all patches that need
testing are clearly marked as such.
if someone wants to provide me with hardware (temporarily or
permanently), go ahead (i'm in berlin, germany).
on CC is everyone who is recorded to have hacked the emu1010 part of the
driver or tested something. i fully expect half the addresses to bounce,
and the remainder to wonder what i'm smoking. ;-)
when you reply, please do so only to the list and me.
regards
next reply other threads:[~2023-02-16 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:33 Oswald Buddenhagen [this message]
2023-03-08 5:32 ` [PATCH 0/130+] ALSA: emu10k1 & more 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=Y+4UcetSxH6lDPoy@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=James@superbug.co.uk \
--cc=alex@samad.com.au \
--cc=alsa-devel@alsa-project.org \
--cc=c.fertr@gmail.com \
--cc=dustin@seznam.cz \
--cc=maligor@gmail.com \
--cc=mcdebugger@duganet.ru \
--cc=michael@gernoth.net \
--cc=rlrevell@joe-job.com \
--cc=shane-alsa@cm.nu \
--cc=thomasz@hostmaster.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox