From: Jan Depner <eviltwin69@cableone.net>
To: The Linux Audio Developers' Mailing List
<linux-audio-dev@music.columbia.edu>
Cc: Giuliano Pochini <pochini@denise.shiny.it>,
Amaury Jacquot <sxpert@esitcom.org>,
Audio-User <linux-audio-user@music.columbia.edu>,
alsa-devel <alsa-devel@lists.sourceforge.net>,
Steve Harris <S.W.Harris@ecs.soton.ac.uk>
Subject: Re: [linux-audio-dev] Re: Firewire Audio Card Support
Date: Thu, 18 Nov 2004 16:49:29 -0600 [thread overview]
Message-ID: <1100818169.3464.6.camel@eviltwin> (raw)
In-Reply-To: <1100809010.10150.5.camel@krustophenia.net>
That is a damn good rant! I agree completely. Unfortunately I only do
software :-/
Jan
On Thu, 2004-11-18 at 14:16, Lee Revell wrote:
> On Thu, 2004-11-18 at 16:09 +0100, Giuliano Pochini wrote:
> > No, it's not hard because there are a lot of skilled people around, but
> > the card would be expensive. There was a thread about a project of "open
> > source" graphic card recently on lkml.
>
> And I posted a [possibly OT] rant to that thread about how this was a
> waste of time and how you could REALLY make a killing with open sound
> hardware.
>
> http://lkml.org/lkml/2004/10/23/292
>
> I got one "right on, brother" response via private mail and that was it.
> But then again half the kernel guys don't have sound cards in their
> machines ;-)
>
> Lee
>
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-18 22:49 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 ` [Alsa-devel] " Takashi Iwai
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 [this message]
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=1100818169.3464.6.camel@eviltwin \
--to=eviltwin69@cableone.net \
--cc=S.W.Harris@ecs.soton.ac.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
--cc=pochini@denise.shiny.it \
--cc=sxpert@esitcom.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