Re: [Alsa-devel] Converted "Writing an ALSA Driver" to DocBook.

2003-01-03 Thread Patrick Shirkey
Patrick Shirkey wrote: nice. if you finish the set up, please let me know the url. i'll add it as the reference to the new version. Kevin sent me the html version and I have added it and the sgml file to the site. http://www.alsa-project.org/documentation.php3 The link to the html is htt

Re: [Alsa-devel] ymfpci, big-endian, and spdif out

2003-01-03 Thread Jaroslav Kysela
On Thu, 2 Jan 2003, Troy Benjegerdes wrote: > I have a mac G4 (running debian testing), a ymfpci card (MaxiSound > Fortissimo) with optical TOSlink out, and a yamaha HTR-5540 receiver with > digital optical TOSlink input. > > I'm trying to get xine or some other DVD player to output AC/3 sound to

[Alsa-devel] cmipci problem

2003-01-03 Thread Martin Langer
Hi, cmipci.c doesn't compile using CVS from today. Hmm, "global_list" is a little bit strange there I think bye, martin In file included from cmipci.c:1: ../alsa-kernel/pci/cmipci.c: In function snd_cmipci_create': ../alsa-kernel/pci/cmipci.c:2957: warning: assignment from incompati

[Alsa-devel] Digital sound card conventions

2003-01-03 Thread Anders Torger
I'm doing a maintenance update on the rme96 driver, and I wonder if there are any conventions to follow in the driver concerning digital sound cards. The specific questions are how to handle sample rates and sound formats on the input. The sound card supports several sample rates and formats.

[Alsa-devel] Re: Digital sound card conventions

2003-01-03 Thread Jaroslav Kysela
On Fri, 3 Jan 2003, Anders Torger wrote: > I'm doing a maintenance update on the rme96 driver, and I wonder if > there are any conventions to follow in the driver concerning digital > sound cards. > > The specific questions are how to handle sample rates and sound formats > on the input. > >

Re: [Alsa-devel] Re: Digital sound card conventions

2003-01-03 Thread Anders Torger
On Friday 03 January 2003 21.33, Jaroslav Kysela wrote: > On Fri, 3 Jan 2003, Anders Torger wrote: > > I'm doing a maintenance update on the rme96 driver, and I wonder if > > there are any conventions to follow in the driver concerning > > digital sound cards. > > > > The specific questions are how

Re: [Alsa-devel] Re: Digital sound card conventions

2003-01-03 Thread Paul Davis
> >This part of PCM API has not been discussed. I think that we should follow >the most easy way: It is - allow only sample rate given by application, if >the master clock is using another sample rate - in trigger() callback - >driver will fail. this seems wrong to me. what should fail is an atte

Re: [Alsa-devel] Re: Digital sound card conventions

2003-01-03 Thread Anders Torger
On Friday 03 January 2003 22.47, Paul Davis wrote: > >This part of PCM API has not been discussed. I think that we should > > follow the most easy way: It is - allow only sample rate given by > > application, if the master clock is using another sample rate - in > > trigger() callback - driver will

[Alsa-devel] How to support multiple open in low-level driver

2003-01-03 Thread Anders Torger
I have noticed that some (most) low level drivers support multiple open, that is a sound card which is already opened, can be opened again. I noticed that also my rme96 driver supported this sort of, although it probably does not feel very good about it. If the sound card is in ADAT mode, it i

[Alsa-devel] cs46xx - Terratec DMX XFire 1024

2003-01-03 Thread Patrick Shirkey
[EMAIL PROTECTED] wrote: The following has been submitted as a note for the documentation of cs46xx. Richard Stevens Friday, 03 January 2003 Terratec DMX XFire 1024: The DMX XFire 1024 doesn't get initialized correctly the first time the alsa modules are l