From: Paul Barton-Davis <pbd@Op.Net>
To: linux-sound@vger.kernel.org
Subject: Re: 4D-NXs (was Re: Sync Issues)
Date: Thu, 28 Oct 1999 12:39:51 +0000 [thread overview]
Message-ID: <marc-linux-sound-94111439108601@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94102459902838@msgid-missing>
>> >Still irrelevant to the *statement being made*, which is "*we* dont have
>> >enough programmers to do that". Why has the number of programmers *they*
>> >have, have anything to do with us volunteers writing a driver for them for
>> >free? *boggle*.
>> they don't *want* volunteers writing drivers for them. period. end of story.
>
>If thats what they wanted, why didnt they just say it. Stating it that way
>is purposely deceitful.
the fault is more likely in my wording of it. i wasn't trying to quote
directly. the company concerned has just been burned by having a 3rd
party write drivers for it. i don't think they were deceitful with me,
i just didn't present a very accurate picture of what they said.
>Well one would have to weigh the effort of reverse engineering it against
>the gains. Is there any point reverse engineering such ancient hardware?
>Compared to eg reverse engineering the emu10k or aureal chips.
what do you think the expected lifetime of any of the current
generation of chips is, given how long every previous equivalent has
lasted ? if we're reverse engineering a chip more than 18mths after
its first use in a PC soundcard, i'd say we might well be wasting our
time, in the long haul.
>FWIW the SAM9407 documentation was pretty inadequate but gerd rausch
>managed to come up with a pretty decent driver anyway.
well, mine works just fine. its just that the non-linear relationships
between the memory locations on the DSP make it more or less useless
to try to use the driver to alter the operation of the downloaded
microprogram unless you're interested in random FX :) instead, you get
the DSP in something close to passthru mode.
--p
next prev parent reply other threads:[~1999-10-28 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 11:40 4D-NXs (was Re: Sync Issues) Billy Biggs
1999-10-27 11:54 ` Jaroslav Kysela
1999-10-27 13:53 ` Paul Barton-Davis
1999-10-27 20:06 ` Dan Hollis
1999-10-27 22:53 ` David Olofson
1999-10-28 0:04 ` Paul Barton-Davis
1999-10-28 0:23 ` Dan Hollis
1999-10-28 0:38 ` Paul Barton-Davis
1999-10-28 0:50 ` Dan Hollis
1999-10-28 2:46 ` John Littler
1999-10-28 12:39 ` Paul Barton-Davis [this message]
1999-10-28 18:33 ` Dan Hollis
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=marc-linux-sound-94111439108601@msgid-missing \
--to=pbd@op.net \
--cc=linux-sound@vger.kernel.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