Linux Sound subsystem development
 help / color / mirror / Atom feed
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 00:38:58 +0000	[thread overview]
Message-ID: <marc-linux-sound-94107113701231@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.

>No, Yamaha *does* have documentation on the native PCI stuff. They just
>wont release it.

i have been told by one senior level management guy at yamaha and one
senior programming guy from their main japanese plant that there is
*NO* documentation for the DSP Factory.

>Im more concerned about chip vendors than card manufacturers. If we
>convince the chip vendor to release docs then theres really nothing a card
>manufacturer can do to stop us.

i have the "full specs" to the (ancient) YSS225 FX processor from
yamaha. its installed on the Tropez+. the specs are useless because it
has downloaded microcode to set it up, and they only document 5
microcode programs. Yamaha wrote a special one for Turtle Beach, and
neither they nor Yamaha appear have any record of what it used the dsp
memory locations for.

i've used dosemu to decode part of it, and reverse engineered the
windows FX driver too, but the end result is a GUI with 512 buttons
that inc/dec values in a DSP location to let me try to understand what
it does. since many memory locations' function is tightly coupled with
several others, its a pretty hopeless case. i did manage to find where
the global stereo echo delay time was set, but that was all.

you could argue that this means that we don't have the specs, but
Yamaha certainly doesn't see it that way.

--p

  parent reply	other threads:[~1999-10-28  0:38 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 [this message]
1999-10-28  0:50 ` Dan Hollis
1999-10-28  2:46 ` John Littler
1999-10-28 12:39 ` Paul Barton-Davis
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-94107113701231@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