Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001052]: Riptide/Context Audio Drivers
Date: Wed, 13 Apr 2005 22:01:07 +0200	[thread overview]
Message-ID: <8abbe1059221db40640ded40f40d8b5f@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1052> 
======================================================================
Reported By:                JKnife
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Issue ID:                   1052
Category:                   ISA - GUS (classic, max, extreme, interwave)
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Distribution:               
Kernel Version:             
======================================================================
Date Submitted:             04-13-2005 21:59 CEST
Last Modified:              04-13-2005 22:01 CEST
======================================================================
Summary:                    Riptide/Context Audio Drivers
Description: 
there is a set but its only for the 2.4 kernel.
i would like you toinclude them in alsa.
the 2.4 drivers can be found here
http://www.linuxant.com/drivers/
======================================================================

----------------------------------------------------------------------
 JKnife - 04-13-05 22:01 
----------------------------------------------------------------------
opps i for got to set cat.. srry

Issue History
Date Modified  Username       Field                    Change              
======================================================================
04-13-05 21:59 JKnife         New Issue                                    
04-13-05 22:01 JKnife         Note Added: 0004479                          
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-04-13 20:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 20:01 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 16:48 [ALSA - driver 0001052]: Riptide/Context Audio Drivers bugtrack
2005-07-22 10:24 bugtrack
2005-07-08 12:57 bugtrack
2005-06-27 16:35 bugtrack
2005-06-26 20:48 bugtrack
2005-06-24 13:09 bugtrack
2005-06-23 13:35 bugtrack
2005-06-23 13:26 bugtrack
2005-06-23 13:21 bugtrack
2005-06-23 13:10 bugtrack
2005-06-23 10:07 bugtrack
2005-06-15 12:41 bugtrack
2005-06-08 21:25 bugtrack
2005-06-08 13:15 bugtrack
2005-06-06  8:51 bugtrack
2005-04-13 19:59 bugtrack

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=8abbe1059221db40640ded40f40d8b5f@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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