From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001293]: trident: device supported by OSS but not by ALSA
Date: Thu, 12 Jan 2006 23:38:05 +0100 [thread overview]
Message-ID: <3d019a9a7e97df3ef8452e7dea8df6e7@bugtrack.alsa-project.org> (raw)
The following issue requires your FEEDBACK.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1293>
======================================================================
Reported By: Adrian Bunk
Assigned To: rlrevell
======================================================================
Project: ALSA - driver
Issue ID: 1293
Category: PCI - trident
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Distribution:
Kernel Version: 2.6.13-rc4-mm1
======================================================================
Date Submitted: 07-31-2005 21:13 CEST
Last Modified: 01-12-2006 23:38 CET
======================================================================
Summary: trident: device supported by OSS but not by ALSA
Description:
I'm currently creating a list of OSS drivers where all the hardware
supported by them is also supported by ALSA. The goal is to schedule
them for removal (except someone tells that for one or more of them ALSA
support is inferior). I do not have this hardware, but this is currently
the reason why the old OSS driver can't be removed from the kernel.
The OSS trident driver has 5 different pci_device_id entries.
For 4 of them there seems to be similar ALSA support, but I can't find
any ALSA equivalent for the following entry:
{PCI_VENDOR_ID_INTERG, PCI_DEVICE_ID_INTERG_5050,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, CYBER5050},
Alan Cox said about this:
The OSS driver supports the CyberPro T-squared core integrated into the
cyberpro chipset while the ALSA driver only supports the others. Should
be easy for someone to resolve. I don't have any 5000 hardware to test
it however.
======================================================================
----------------------------------------------------------------------
pwaechtler - 08-22-05 10:05
----------------------------------------------------------------------
The cyberpro 5050 is an old combined video+audio controller - and is/was
used in some settop boxes (German Siemens Activity and also Loewe).
There will be no "desktop users" around.
And because I don't work for Loewe anymore: I don't have access to
hardware.
If you ask me: leave it out!
----------------------------------------------------------------------
rlrevell - 01-12-06 23:38
----------------------------------------------------------------------
Still no testers. If we don't find one via LKML we can probably close
this.
Issue History
Date Modified Username Field Change
======================================================================
07-31-05 21:13 Adrian Bunk New Issue
07-31-05 21:13 Adrian Bunk Kernel Version => 2.6.13-rc4-mm1
08-03-05 12:01 perex Note Added: 0005616
08-22-05 10:05 pwaechtler Note Added: 0005890
01-12-06 23:38 rlrevell Note Added: 0007592
01-12-06 23:38 rlrevell Assigned To => rlrevell
01-12-06 23:38 rlrevell Status new => feedback
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-12 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 22:38 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 22:56 [ALSA - driver 0001293]: trident: device supported by OSS but not by ALSA bugtrack
2005-08-22 8:05 bugtrack
2005-08-03 10:01 bugtrack
2005-07-31 19:13 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=3d019a9a7e97df3ef8452e7dea8df6e7@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