From: Fred Gleason <fredg@salemradiolabs.com>
To: Eliot Blennerhassett <bigblen@icqmail.com>,
alsa-devel@lists.sourceforge.net
Cc: linux@blennerhassett.gen.nz
Subject: Re: Upgrade driver to 1.0.6, memory allocation?
Date: Thu, 19 Aug 2004 09:01:48 -0400 [thread overview]
Message-ID: <200408190901.48652.fredg@salemradiolabs.com> (raw)
In-Reply-To: <505401c48598$4a891ec0$72cb010a@mail2world.com>
On Wednesday 18 August 2004 22:57, Eliot Blennerhassett wrote:
> Is there a rationale for making the substreams limit 4 as opposed to any
> other number?
I take it these streams map one-to-one with HPI stream resources? If four is
the limit, what happens if there are already four or more streams open via
HPI? Would snd_pcm_open() fail, or could the driver 'redirect' in some way
to an unused stream?
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Director of Broadcast Software Development |
| | Salem Radio Labs |
|-------------------------------------------------------------------------|
| Some people say a front-engine car handles best. Some people say a |
| rear-engine car handles best. I say a rented car handles best. |
| --P.J. O'Rourke |
|-------------------------------------------------------------------------|
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-19 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 2:57 Upgrade driver to 1.0.6, memory allocation? Eliot Blennerhassett
2004-08-19 7:49 ` Giuliano Pochini
2004-08-19 13:01 ` Fred Gleason [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 2:57 Eliot Blennerhassett
2004-08-19 9:53 ` Takashi Iwai
2004-08-19 2:57 Eliot Blennerhassett
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=200408190901.48652.fredg@salemradiolabs.com \
--to=fredg@salemradiolabs.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bigblen@icqmail.com \
--cc=linux@blennerhassett.gen.nz \
/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.