mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: To:  Joseph Fannin <jhf@rivenstone.net>,
	Shawn Starr <spstarr@sh0n.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM][SOUND][2.5] - ALSA & OSS cannot find SBAWE32 Card
Date: Wed, 27 Nov 2002 20:05:59 +0000	[thread overview]
Message-ID: <20021127200559.GA6305@neo.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0211261044070.1462-100000@montezuma.mastecende.com>

On Tue, Nov 26, 2002 at 10:47:03AM -0500, Zwane Mwaikambo wrote:
> On Tue, 26 Nov 2002, Joseph Fannin wrote:
> 
> > On Tue, Nov 26, 2002 at 02:58:05AM -0500, Shawn Starr wrote:
> >
> > > ALSA device list:
> > >    No soundcards found.
> > >
> > > dmesg 2.4.20-pre7 - OSS: - WORKS
> > > ============================
> >
> >     Me too!
> >
> >     In 2.5.47 mainline and 2.5.49-ac1 the ALSA drivers (either sb16 or
> > sbawe) load but don't detect devices if PNP support is built in.  The
> > same card (an awe64) works fine under 2.4.19.
> >
> >     Without PNP sb16 works (with only sb16 features) but sbawe will
> > not load, complaining that it can't find the awe bits.
> 
> My guess would be the new isapnp registration layer, which ALSA
> doesn't seem to be using. I might have a go at it later, looks like it
> might need conversion.
> 
> Cheers,
> 	Zwane

That is indeed the case.  I just released a patch for pnp card support.
This new API can be used to convert these drivers.

Thanks,
Adam

  reply	other threads:[~2002-11-28  1:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  7:58 Shawn Starr
2002-11-26  8:58 ` Joseph Fannin
2002-11-26 15:47   ` Zwane Mwaikambo
2002-11-27 20:05     ` Adam Belay [this message]
2002-11-28  5:00       ` Paul Laufer
2002-11-28  5:06         ` Shawn Starr

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=20021127200559.GA6305@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=jhf@rivenstone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spstarr@sh0n.net \
    --cc=zwane@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®