From: Pieter Palmers <pieterp@joow.be>
To: Claus Riethmueller <claus@esi-audio.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ESI reply!! (MAYA44 datasheet request)
Date: Wed, 22 Aug 2007 20:02:24 +0200 [thread overview]
Message-ID: <46CC7A30.9020803@joow.be> (raw)
In-Reply-To: <20070822152207.5959424468@alsa0.perex.cz>
Claus Riethmueller wrote:
...
>
>> Now, if ESI cannot even provide this, we should highlight ESI in RED in
>> the sound card matrix.
>
> As you can guess, it was this sentence that prompted me to reply directly to
> the list. In my opinion, your comment is unfair and simply ignoring major
> parts of what I wrote in my mail to Piotr. I have shown a certain level of
> commitment and your response basically tells me that you are not even
> interested ... if more people would share your views, ALSA would have made
> no development at all in the last 5 years I guess.
>
I think it is only fair to mention that for FreeBoB, ESI was the first
company to provide us with hardware to develop with. They provided us
with a QuataFire610 even before we had a single line of code. Compared
to the hassle we experience with other vendors, even to date, I consider
this a very open and constructive attitude.
Greets,
Pieter Palmers
FreeBoB/FFADO developer
next prev parent reply other threads:[~2007-08-22 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 15:22 ESI reply!! (MAYA44 datasheet request) Claus Riethmueller
2007-08-22 16:03 ` Adrian McMenamin
2007-08-22 17:58 ` Rene Herman
2007-08-22 18:02 ` Pieter Palmers [this message]
2007-08-22 21:50 ` Takashi Iwai
2007-08-22 22:09 ` Rene Herman
2007-08-22 22:42 ` Takashi Iwai
2007-08-23 2:17 ` Tobin Davis
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 6:52 Piotr Makowski
2007-08-22 7:05 ` Piotr Makowski
2007-08-22 13:38 ` James Courtier-Dutton
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=46CC7A30.9020803@joow.be \
--to=pieterp@joow.be \
--cc=alsa-devel@alsa-project.org \
--cc=claus@esi-audio.com \
/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