All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: perex@suse.cz, mulix@mulix.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, Alan Cox <alan@redhat.com>
Subject: Re: Device supported by the OSS trident driver not supported by ALSA
Date: Mon, 25 Jul 2005 00:42:49 +0100	[thread overview]
Message-ID: <1122248569.10835.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20050723200417.GI3160@stusta.de>

On Sad, 2005-07-23 at 22:04 +0200, Adrian Bunk wrote:
> 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},
> 
> Can anyone tell my why this device is supported by the OSS trident 
> driver but not by ALSA?

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.

Alan



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: perex@suse.cz, mulix@mulix.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, Alan Cox <alan@redhat.com>
Subject: Re: Device supported by the OSS trident driver not supported by ALSA
Date: Mon, 25 Jul 2005 00:42:49 +0100	[thread overview]
Message-ID: <1122248569.10835.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20050723200417.GI3160@stusta.de>

On Sad, 2005-07-23 at 22:04 +0200, Adrian Bunk wrote:
> 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},
> 
> Can anyone tell my why this device is supported by the OSS trident 
> driver but not by ALSA?

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.

Alan


  reply	other threads:[~2005-07-24 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23 20:04 Device supported by the OSS trident driver not supported by ALSA Adrian Bunk
2005-07-23 20:04 ` Adrian Bunk
2005-07-24 23:42 ` Alan Cox [this message]
2005-07-24 23:42   ` Alan Cox

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=1122248569.10835.22.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    --cc=perex@suse.cz \
    /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.