All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Hannu Savolainen <hannu@opensound.com>
Cc: Cody Jung <funkycat32@gmail.com>,
	alsa-devel@alsa-project.org, alsa-user@alsa-project.org
Subject: Re: [Alsa-user] ALSA Newbie - Getting Ensoniq	SoundscapeVivo to work?
Date: Sun, 29 Apr 2007 00:39:30 +0200	[thread overview]
Message-ID: <4633CD22.9070305@gmail.com> (raw)
In-Reply-To: <4633356F.9090404@opensound.com>

On 04/28/2007 01:52 PM, Hannu Savolainen wrote:

> Wrong. VIVO and VIVO90 are different models but I can't remember exactly 
> what was the difference (maybe VIVO90 was PnP and VIVO just plain ISA).

Okay, thank you for the information. The one I have here has a large sticker 
on it saying "Soundscape VIVO90" but "ENSONIQ SoundscapeVIVO" as the PNP ID 
so I assumed they were probably the same thing...

> Both models were supported by earlier versions of OSS (not OSS/Free). ISA
> drivers are no longer included in OSS but older 3.9.8 version (requires
> 2.4.x kernel) still has it.

Given that OSS no longer supports ISA drivers -- no source for these would 
be available, would it? I have a specific hobby interest in these old ISA 
soundcards.

Rene.

  reply	other threads:[~2007-04-28 22:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d382e1990704272206y9712a84x1e07d07eda58fb18@mail.gmail.com>
2007-04-28  9:54 ` [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work? Rene Herman
2007-04-28 11:52   ` Hannu Savolainen
2007-04-28 22:39     ` Rene Herman [this message]
     [not found]       ` <d382e1990704281918g42165aaas4cac717fe5b4bab0@mail.gmail.com>
2007-04-29  7:31         ` Rene Herman
2007-04-29  7:33           ` Rene Herman
2007-04-28 15:56   ` Cody Jung
2007-04-28 22:32     ` [Alsa-user] " Rene Herman

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=4633CD22.9070305@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@alsa-project.org \
    --cc=funkycat32@gmail.com \
    --cc=hannu@opensound.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.