All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@op.net>
To: alsa-devel@alsa-project.org
Subject: snd-rme9652_mem and the H-DSP
Date: Thu, 9 May 2002 08:57:29 -0400	[thread overview]
Message-ID: <200205091257.g49CvTO16266@op.net> (raw)

both the hammerfall and hammerfall-dsp require exactly the same kind
of memory allocation. the snd-rme9652_mem module, which allocates
a contiguous chunk of about 1.2MB of physical RAM, uses the "driver
index" to identify which snd-card is using a given buffer. this means
that if we try to use both a hammerfall and a hammerfall-dsp, things
don't work: both drivers pass "driver index" = 0 to the memory
module, and the second try (whatever it is) concludes that it already
has buffers allocated.

i propose using the card->number value instead, so that the numbers are
unique across all driver modules. 

the only other option i can see is to duplicate the code in
snd-rme9652_mem, which seems really dumb.

i also propose renaming the module to snd-hammerfall_mem to clearly
indicate its generic status, and moving it into its own directory. it
will be built if either CONFIG_SND_CARD_RME9652 and/or
CONFIG_SND_CARD_HDSP are defined.

let me know if this sounds like the right solution, or if you have a
better one.

--p




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

             reply	other threads:[~2002-05-09 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09 12:57 Paul Davis [this message]
2002-05-09 14:43 ` snd-rme9652_mem and the H-DSP Jaroslav Kysela
2002-05-13 10:18   ` Takashi Iwai
2002-05-14  1:59     ` Paul Davis
2002-05-14  2:07       ` 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=200205091257.g49CvTO16266@op.net \
    --to=pbd@op.net \
    --cc=alsa-devel@alsa-project.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 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.