Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Benno Senoner <sbenno@gardena.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: max SNDRV_CARDS bug ? questions ....
Date: Wed, 03 Dec 2003 14:05:44 +0100	[thread overview]
Message-ID: <s5had6acaqf.wl@alsa2.suse.de> (raw)
In-Reply-To: <3FCE32B5.1030208@gardena.net>

At Wed, 03 Dec 2003 20:00:05 +0100,
Benno Senoner wrote:
> 
> Hi,
> (I'm using alsa-driver-1.0.0rc1)
> 
> I have a question about the SNDRV_CARDS.
> normally it is defined as 8
> ./alsa-kernel/core/memalloc.c: #define SNDRV_CARDS     8
> 
> Does that mean we can have a maximum of 8 soundcards
> in the PC or is this simply how many instances a certain module supports ?
> (eg I could have 8 emu10k instances, 8 sb16 instances etc ?).

no, totally 8 instances.  not the number of modules.

> Plus I noticed something in
> 
> ./alsa-kernel/core/memalloc.c: static int enable[8] = {[0 ... 
> (SNDRV_CARDS-1)] = 1};
> 
> shouldn't that be:
> static int enable[SNDRV_CARDS] = {[0 ... (SNDRV_CARDS-1)] = 1};     ?

yes, but not a bug as long as SNDRV_CARDS = 8 :)

> is this a bug ? what happens if we set SNDRV_CARDS to a value > 8 ?

more than 8 cards are not supported in the current assignment of
devices.  the minor devices will be out of range.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-12-03 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 19:00 max SNDRV_CARDS bug ? questions Benno Senoner
2003-12-03 13:05 ` Takashi Iwai [this message]
2003-12-03 22:25   ` Max # of cards, pcm devices, midi devices Was: " Benno Senoner

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=s5had6acaqf.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=sbenno@gardena.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox