From: "Eliot Blennerhassett" <bigblen@xtra.co.nz>
To: Dan Hollis <goemon@anime.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Writing a driver for this card: your thoughts?
Date: Fri, 7 Jun 2002 13:00:05 +1200 [thread overview]
Message-ID: <3D00AE55.11120.9CD4ED3@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0206061155230.15480-100000@sasami.anime.net>
On 6 Jun 2002 at 12:04, Dan Hollis wrote:
> Is it possible to bundle DSP firmware code with the driver? (If it's
> uploaded by the host, and it's not in eeprom or something). It's very hard
> to distribute drivers for firmware-based devices if we can't distribute
> the firmware required :-o
Yes. The firmware image is currently loaded from a binary data file which is
distributed as part of our current drivers.
> But we don't need the source code to the DSP firmware. Just tell us how to
> talk to the DSP and tell it to make noise.
I'll work out what info/code we would need to release, and see if this is
something management would agree to.
> It looks pretty nice. But what's the price? :-o
Models range from $995 to $3495
:-O no, they aren't competition for a soundblaster...
> What's minimum latency possible with the card?
Historically our cards have very large buffers that contain seconds of audio, so
that they can keep playing flawlessly even if the CPU or network gets bogged
down. Whether this is used or not is up to the application though.
Low latency has not been a design goal. I would say the latency is between
about 3000 to 5000 samples depending on processing details.
>
> -Dan
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next prev parent reply other threads:[~2002-06-07 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 23:03 Writing a driver for this card: your thoughts? Eliot Blennerhassett
2002-06-06 19:04 ` Dan Hollis
2002-06-07 1:00 ` Eliot Blennerhassett [this message]
2002-06-07 1:39 ` Dan Hollis
2002-06-10 14:20 ` Takashi Iwai
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=3D00AE55.11120.9CD4ED3@localhost \
--to=bigblen@xtra.co.nz \
--cc=alsa-devel@lists.sourceforge.net \
--cc=goemon@anime.net \
/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.