From: James Courtier-Dutton <James@superbug.co.uk>
To: Piotr Makowski <oponek@gmail.com>
Cc: alsa-devel@alsa-project.org,
"Pawe? Wolniewicz" <admin@linux-muzyka.ixion.pl>
Subject: Re: ESI reply!! (MAYA44 datasheet request)
Date: Wed, 22 Aug 2007 14:38:41 +0100 [thread overview]
Message-ID: <46CC3C61.8040702@superbug.co.uk> (raw)
In-Reply-To: <87988a970708212352r166efc80k99eca3575e96fbd1@mail.gmail.com>
Piotr Makowski wrote:
> Hi Piotr,
>
> thank you very much for your email.
> The data sheet and information you request does not exist in any format that
> we could provide and frankly, we are way too busy with our normal work to
> prepare something like that in a way that would be of general use and would
> resemble what you require in your request.
>
<snip>
> Please don't get me wrong, I understand what you want and where you are
> coming from, but this direct contact with the developer is a basic
> requirement for us - sorry.
> Best regards,
> Claus Riethmueller
> Managing Director ESI Audiotechnik GmbH
>
Hi,
So, basically, ESI cannot help us.
I am amazed that they can write any sort of driver without some sort of
datasheet.
But I do know it does happen, because I have received datasheets that
were only written years after a particular sound card was first sold.
I would like to stress, that the datasheet does not have to be perfect.
We would be quite happy if it has spelling mistakes in, and some wrongly
labeled registers.
I have received datasheets from other manufactures where some engineer
has just scribbled some notes on the back of a piece of paper.
The important point I am trying to make is that the data about the sound
card does not have to prettily laid out or even 100% accurate. We just
need something that helps save us time in developing a driver. Ideally,
it should be in some editable electronic format, so that ALSA developers
can edit and correct errors in the document as and when they find them.
Now, if ESI cannot even provide this, we should highlight ESI in RED in
the sound card matrix.
Kind Regards
James
next prev parent reply other threads:[~2007-08-22 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:52 ESI reply!! (MAYA44 datasheet request) Piotr Makowski
2007-08-22 7:05 ` Piotr Makowski
2007-08-22 13:38 ` James Courtier-Dutton [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 15:22 Claus Riethmueller
2007-08-22 16:03 ` Adrian McMenamin
2007-08-22 17:58 ` Rene Herman
2007-08-22 18:02 ` Pieter Palmers
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
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=46CC3C61.8040702@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=admin@linux-muzyka.ixion.pl \
--cc=alsa-devel@alsa-project.org \
--cc=oponek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.