From: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
To: Pieter Palmers
<ppalmers-8ZVx2yYfyutX2QMWbMbClIble9XqW/aP@public.gmane.org>
Cc: Amaury Jacquot <sxpert-3iarmHWDzwRAfugRpC6u6w@public.gmane.org>,
linux-audio-user-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org,
alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org
Subject: Re: [Alsa-devel] Firewire Audio Card Support
Date: Thu, 18 Nov 2004 20:19:42 +0100 [thread overview]
Message-ID: <s5h1xerc6cx.wl@alsa2.suse.de> (raw)
In-Reply-To: <419CFE12.1070908-8ZVx2yYfyutX2QMWbMbClIble9XqW/aP@public.gmane.org>
At Thu, 18 Nov 2004 19:54:58 +0000,
Pieter Palmers wrote:
>
> Why don't we support the manufacturers that do support us? After all,
> there are some that provide us with what we need, and I don't see that
> mentioned that often. I'm quite confident that for most needs you can
> find a card from a manufacturer that supports ALSA development. Correct
> me if I'm wrong, but I got the impression that for example RME and ESI
> actively support the development of ALSA drivers for their producs.
Well, the ALSA support shall be achieved sooner or later :)
But it's true that there is still a significant gap between the
product release and the support on Linux.
Once people recognize the importance of Linux desktop, this gap will
be decreaed, I guess.
My biggest concern is the chaos like what has happend on USB
audio/midi (or look at ACPI). I really hope such a theatrical
confusion won't happen on fireware audio. The precised specification
doesn't always lead to a good result :)
Takashi
next prev parent reply other threads:[~2004-11-18 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31148074.1100630541337.JavaMail.root@scooter.psp.pas.earthlink.net>
[not found] ` <419C9D47.4090606@x-i.net>
[not found] ` <419C9D47.4090606-l4pODZ2nMLw@public.gmane.org>
2004-11-18 14:15 ` Firewire Audio Card Support Olaf Christ
[not found] ` <200411181515.52218.olaf-Cb7RZHV19h6Y/VGTjfr9Sg@public.gmane.org>
2004-11-18 14:32 ` [Alsa-devel] " Steve Harris
2004-11-18 14:44 ` Amaury Jacquot
2004-11-18 15:09 ` Giuliano Pochini
2004-11-18 15:15 ` Amaury Jacquot
2004-11-18 19:54 ` Pieter Palmers
[not found] ` <419CFE12.1070908-8ZVx2yYfyutX2QMWbMbClIble9XqW/aP@public.gmane.org>
2004-11-18 19:19 ` Takashi Iwai [this message]
2004-11-18 20:16 ` Lee Revell
2004-11-18 22:07 ` [linux-audio-dev] " Jens M Andreasen
2004-11-18 22:49 ` Jan Depner
2004-11-18 22:54 ` Re: [linux-audio-dev] Re: [Alsa-devel] " Mark Knecht
2004-11-18 23:52 ` [linux-audio-user] " Florian Schmidt
[not found] ` <1100809010.10150.5.camel-sMXKvD5kdRZ9Itub2Jo68g@public.gmane.org>
2004-11-19 17:12 ` Jussi Laako
[not found] ` <1100884361.13133.10.camel-7xOsYr0MI4rPaj0P+rXokA@public.gmane.org>
2004-11-19 18:37 ` Re: [linux-audio-dev] " Lee Revell
2004-11-19 20:26 ` Re: [linux-audio-user] " Martin Langer
2004-11-20 10:22 ` Giuliano Pochini
2004-11-18 19:36 ` Pieter Palmers
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=s5h1xerc6cx.wl@alsa2.suse.de \
--to=tiwai-l3a5bk7wagm@public.gmane.org \
--cc=alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org \
--cc=linux-audio-user-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org \
--cc=ppalmers-8ZVx2yYfyutX2QMWbMbClIble9XqW/aP@public.gmane.org \
--cc=sxpert-3iarmHWDzwRAfugRpC6u6w@public.gmane.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