Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Jonathan Masters <mastersj@periscope-systems.freeserve.co.uk>
To: linux-sound@vger.kernel.org
Subject: Multiple sbs with module
Date: Thu, 19 Aug 1999 01:08:37 +0000	[thread overview]
Message-ID: <marc-linux-sound-93502551628718@msgid-missing> (raw)

Hi,
    I currently have an SB 64 AWE GOLD PNP set up using the "sb" module
(and it's friends....) with settings IRQ 5. DMA 1 and 5, standard stuff.

    I have a lower spec'd SB 16 (vibra) PNP value card (which *does*
work with Linux as it used to be my main card). I have the two using
resources correctly and have resolved all conflicts. The trouble is, I
must use modules due to the pnp situation with the cards (bios is less
than 6months old (AMI), but it still doesn't get it right if left to
itself) so I have been running isapnp during boot and then adding the sb
driver. However, I now wish to have *2* sb's with the same module. This
would be trivially easy with the code in the kernel (simply setting
SB2_BASE et al), but I must have it in the module. Can this be achieved?
If not, can anyone suggest/provide a patch which will do this/tell me to
upgrade kernel to 2.3.xx etc... I have 2.2.11. Thanx guys. I can't see
this as being impossible it's just that the docs don't mention two cards
with a module.

Jon.

--
Jonathan C. Masters (jonathan@oxlug.org) PGP: www.brookes.ac.uk/~95227860/KEY

"Upon this rock I will build my church
and the gates of hell shall not prevail against it". -- Matthew 16, 17-18

             reply	other threads:[~1999-08-19  1:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-19  1:08 Jonathan Masters [this message]
1999-08-19  1:49 ` Multiple sbs with module Dave Mielke
1999-08-19  1:51 ` Jonathan Masters

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=marc-linux-sound-93502551628718@msgid-missing \
    --to=mastersj@periscope-systems.freeserve.co.uk \
    --cc=linux-sound@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox