Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hannu Savolainen <hannu@opensound.com>
To: Rene Herman <rene.herman@gmail.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: Sat, 28 Apr 2007 14:52:15 +0300	[thread overview]
Message-ID: <4633356F.9090404@opensound.com> (raw)
In-Reply-To: <463319CA.4040309@gmail.com>

Rene Herman kirjoitti:
> On 04/28/2007 07:06 AM, Cody Jung wrote:
>
>   
>> As it suggests in the subject, I'm both a Linux-newbie and an
>> ALSA-newbie. I have an old clunker of a machine running Ubuntu Feisty
>> that I built out of parts left on curbs during spring cleanup, and that's
>> how I came across my sound card. It's an Ensoniq SoundscapeVivo (Not a 
>> Vivo90, AFAIK).
>>     
>
> As far as I'm aware, there are no other VIVO's than the VIVO90.
>   
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). 
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.

Best regards,

Hannu

  reply	other threads:[~2007-04-28 11:52 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 [this message]
2007-04-28 22:39     ` Rene Herman
     [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=4633356F.9090404@opensound.com \
    --to=hannu@opensound.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@alsa-project.org \
    --cc=funkycat32@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox