From: Takashi Iwai <tiwai@suse.de>
To: Loc Ho <loc@pacificconsultants.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Memory Allocation Bug
Date: Thu, 13 May 2004 11:24:05 +0200 [thread overview]
Message-ID: <s5hhdukd6iy.wl@alsa2.suse.de> (raw)
In-Reply-To: <D22B281CC561444AA27F7F6C6C9E3E6102F546@mtvs4.pcllc.net>
At Wed, 12 May 2004 18:40:05 -0700,
Loc Ho wrote:
>
> Hi,
>
> I developed an custom USB Audio driver. In addition, I am also using
> the provided USB Audio driver for commercial USB Audio devices. After
> some testing with the custom USB Audio driver and the provided USB
> Audio driver, there seem to be a problem with the ALSA memory
> allocation routine. In file pcm_memory.c function setup_pcm_id, the id
> is generated using the pcm device ID, stream ID, and substream
> number. This only guarantee that the memory tag ID is unique for one
> card. If I have multiple cards, they will not be unique. Am I correct?
no, usually you have a unique struct device pointer for each card, so
it's no problem. the tag is a pair of device pointer and id number.
however, if the same struct device is shared among multiple card
instances, you'll need to set up the id field by yourself. an
exmample is found in mixart driver.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-13 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 1:40 ALSA Memory Allocation Bug Loc Ho
2004-05-13 9:24 ` Takashi Iwai [this message]
[not found] <D22B281CC561444AA27F7F6C6C9E3E6102F548@mtvs4.pcllc.net>
2004-05-13 17:54 ` Takashi Iwai
[not found] <D22B281CC561444AA27F7F6C6C9E3E6102F549@mtvs4.pcllc.net>
2004-05-13 18:06 ` Takashi Iwai
2004-05-13 18:18 ` 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=s5hhdukd6iy.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=loc@pacificconsultants.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.