From: "Jörn Nettingsmeier" <nettings@stackingdwarves.net>
To: alsa-devel@alsa-project.org, Adrian Knoth <adi@drcomp.erfurt.thur.de>
Subject: Re: [PATCH] hdspm.c: make driver name generic to avoid user confusion
Date: Tue, 07 Jun 2011 12:46:03 +0200 [thread overview]
Message-ID: <4DEE016B.7010308@stackingdwarves.net> (raw)
In-Reply-To: <20110607091132.GI17989@ltw.loris.tv>
On 06/07/2011 11:11 AM, Adrian Knoth wrote:
> "HDSPe" is also confusing, only referring to the PCIe versions. Since we
> also support the old PCI versions, I suggest to name it
>
> "RME Hammerfall HDSP(e) Series"
>
> On the other hand, the 'H' in "HDSP" stands for "Hammerfall", so
>
> "RME HDSP(e) Series"
>
> would be more appropriate. Luckily, we don't collide with the hdsp.c
> driver name, but still, it's misleading, because there are cards that
> match "RME HDSP(e) Series" (like the Multiface/Digiface) but are handled
> by hdsp.c instead.
>
> What at mess. ;) Merging hdsp.c into hdspm.c would be the clean approach
> to this problem, still I don't have time for this in the near future.
> Maybe in July.
>
>
> Given that all current variants are misleading in one way or another, we
> could also leave everything as is. What do you think?
no. MADI is way too specific, and the only reason it's there is that
winni started with just the MADI card...
enumerate supported cards? "RME HDSP AES32, AIO, RayDAT, MADI, MADIface"
kludgy, but less potential for user confusion.
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487
Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister (VDT)
http://stackingdwarves.net
next prev parent reply other threads:[~2011-06-07 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DEDE4E2.4060303@folkwang-hochschule.de>
2011-06-07 9:11 ` [PATCH] hdspm.c: make driver name generic to avoid user confusion Adrian Knoth
2011-06-07 10:39 ` Takashi Iwai
2011-06-07 12:13 ` Takashi Iwai
2011-06-14 7:00 ` Takashi Iwai
2011-06-07 10:46 ` Jörn Nettingsmeier [this message]
2011-06-07 8:48 Jörn Nettingsmeier
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=4DEE016B.7010308@stackingdwarves.net \
--to=nettings@stackingdwarves.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).