From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Davis Subject: snd-rme9652_mem and the H-DSP Date: Thu, 9 May 2002 08:57:29 -0400 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <200205091257.g49CvTO16266@op.net> Return-path: Received: from newmx1.fast.net (newmx1.fast.net [209.92.1.31]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id OAA26246 for ; Thu, 9 May 2002 14:56:38 +0200 Received: from unknown (HELO op.net) ([209.92.99.108]) (envelope-sender ) by newmx1.fast.net (qmail-ldap-1.03) with SMTP for ; 9 May 2002 12:56:31 -0000 Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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