All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: Rene Herman <rene.herman@gmail.com>
Cc: Krzysztof Helt <krzysztof.h1@gmail.com>,
	ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: Ensoniq SoundScape VIVO90
Date: Fri, 14 Sep 2007 17:06:55 +0100 (BST)	[thread overview]
Message-ID: <44760.17962.qm@web52902.mail.re2.yahoo.com> (raw)
In-Reply-To: <46EAADFD.20304@gmail.com>

--- Rene Herman <rene.herman@gmail.com> wrote:
> On 09/14/2007 05:17 PM, Chris Rankin wrote:
> > I naturally tested this driver with the only Ensoniq SoundScape card that
> > I owned (the PnP version), and yes, it works. All I did was convert as
> > much of the original OSS driver to ALSA as I could verify.
> 
> Great, thanks for the answer. The 3081 is a little different resource wise 
> then. It finds the codec at "mpu_port" + 8, whereas the VIVOs (4081) has it 
> as a seperate PnP resource.
> 
> 3081:	Soundscape/MPU	port = pnp_port(0),	irq = pnp_irq(1)
> 	Codec		port = + 8,		irq = pnp_irq(0)
> 
> 4081:	Soundscape/MPU	port = pnp_port(0),	irq = pnp_irq(1)
> 	Codec		port = pnp_port(1),	irq = pnp_irq(0)
> 
> It's possible to switch behaviour on the PnP ID (for example by setting 
> pnp_card_device_id->driver_data in the ID table).

Do you have the old OSS SoundScape driver code, and did it support the VIVO? I seem to recall that
there were several extra code-paths in there for other SoundScape versions.

Cheers,
Chris



      _______________________________________________________
Try Yahoo! Mail now with Unlimited Storage and see the difference.
http://uk.mail.yahoo.com

  reply	other threads:[~2007-09-14 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  8:12 Ensoniq SoundScape VIVO90 Krzysztof Helt
2007-09-14 14:34 ` Rene Herman
2007-09-14 14:42   ` Krzysztof Helt
2007-09-14 15:17   ` Chris Rankin
2007-09-14 15:51     ` Rene Herman
2007-09-14 16:06       ` Chris Rankin [this message]
2007-09-14 16:21         ` Rene Herman
2007-09-14 16:50     ` Krzysztof Helt

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=44760.17962.qm@web52902.mail.re2.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@gmail.com \
    --cc=rene.herman@gmail.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 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.