Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: karsten wiese <annabellesgarden@yahoo.de>
Cc: Devel Alsa <alsa-devel@lists.sourceforge.net>
Subject: Re: Turtle Beach Pinnacle/Fiji alsa driver 0.1.2
Date: Fri, 28 Jun 2002 18:05:23 +0200	[thread overview]
Message-ID: <s5h1yaro0cc.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020626143141.52351.qmail@web12208.mail.yahoo.com>

Hi Karsten,

At Wed, 26 Jun 2002 16:31:41 +0200 (CEST),
karsten wiese wrote:
> 
> hi,
> 
> new in this is pcm record and midiin.
> latency (latency -m32 -M32 -b -r 48000, patched to
> allow 3 periods) runs with down to 32 frames.
> amSynth runs well with it on an 400PII. 
> mmap driver for amSynth available from me. 
> not needed, but gives you more voics with the
> fiji/pinnacle.
> 
> 
> works:
> PCM:     Stereo record / playback mmaped fullduplex
> with the alsa-tools aplay, pcm, aplay -M, latency with
> 3 periods patch, alsaplayer, amSynth
> MIXER:   Master, Pcm, Line In, Monitor
> MIDI:    in
> VERSION: 0.9rc2CVS, patch attached
> OS:      tested on Slackware 8.1rc1
> 
> not...yet:
> PCM:     periods / buffer != 3
> MIDI:    out
> SPDIF:
> KURZWEIL: start a mpu401 device
> 
> the patch archive consists off a diff, which is to be
> applied to the raw cvs-sources and two directories.
> after copying the also contained directories into the
> cvs tree do 
> 
> cvscompile 
> make
> make install
> in alsa-driver as usual.
> 
> note: this has only been tested to build modules for a
> 2.4.18 kernel on an 400MHz PII with a pinnacle in
> non-pnp mode.
> 
> 
> 
> For additional infos concerning the fiji/pinnacle
> cards search for the pinnacle oss-free driver docus on
> the web.
> there is a how-to install the needed firmware-files
> also.


thanks, we got finally the support for this old good card.
i'd like to put this stuff into cvs, but before that, could you 
check the following things?


- missing rule for tb-classic module.

  if there are two card modules, will there a common lowlevel
  module for them?  or will be integrated?

- please remove the codes for old kernels.
  the compatibility routines should go to alsa-driver tree, not on
  alsa-kernel tree.

- is there a workaround for the jiffires warp (32bit overflow)?

- please reformat the codes with a certain indent.

- you can use snd_printd() for debug printk.

- it'd be better to keep the uniformity of module parameters like
  other alsa modules, i.e. snd_xxx.

- obviously we can clean up msnd_pinnacle_mixer.c more :)


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf

  reply	other threads:[~2002-06-28 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 14:31 Turtle Beach Pinnacle/Fiji alsa driver 0.1.2 karsten wiese
2002-06-28 16:05 ` Takashi Iwai [this message]
2002-07-06 13:11   ` Turtle Beach Pinnacle/Fiji alsa driver 0.1.3 karsten wiese
2002-07-08 10:29     ` Takashi Iwai
2002-07-09 13:22       ` karsten wiese
2002-07-09 13:33         ` Takashi Iwai

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=s5h1yaro0cc.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    /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