ALSA driver

ALSA driver

[Ulf Carlsson]

Hi all,

I've spent today and yesterday writing an ALSA driver for the HAL2.

Anyhow I'm playing MP3:s on the Indy now (did you hear that puffin?).

I can't say that it sounds good yet, but I can hear what song it is. I'll do
some finetuning now. It shouldn't be hard to fix. It oopses every now and then
as well. I'll consider writing to allocated memory areas instead.. :-)

I'll also implement an interface for the mixer (I don't have any documentation
at all about how the mixer works..?).

- Ulf

ALSA driver

[Manuel Jander]

Hi everyone,

I'm writing a Vortex ALSA driver, recycling most hardware stuff from the 
experimental OSS driver on savannah. I only own a AU8820, but support 
for the other cards shouldnt be difficult, because anything was done 
with portability in mind, and i keep looking into the other cards 
disassembled binary driver from time to time.

Right now the MPU401, ac97 mixer and the gameport work.
PCM audio is still broken, because it causes a system lockup (freeze),
but the good thing is that i actually get sound (one DMA bufer pass).

The au8820-driver (OSS) doesn't has this problem, but it has some buffer 
related bug that causes memory corruption. Mostly repeated open/close 
procedures causes this to happen. The symptoms are random segfaults and 
artifacts on the screen the more i open/close the /dev/dsp file.

Regarding the ALSA driver:
I'm very lost about what could be the problem. It looks like the card
gets stuck, because i tricked the ALSA higher level into thinking the 
DMA was not advancing and it still locked up.
If i comment out the line that starts the FIFO, no lockup occurs and 
anything is fine except that i only get a "tick" instead of audio
playback.

I would like to upload my code somewhere on the CVS, with the hope
soemone can help a bit with this.
Could someone give me write permission on the CVS somewhere else than 
au8820-driver ?

Best Regards

Manuel Jander.



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: ALSA driver (wrong message, sorry).

[Manuel Jander]

Oops, i'm very sorry...  wrong list :-(.
Won't happen again, i swear.
Please excuse my mistake. Was ment for the OpenVortex devel list.




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: ALSA driver (wrong message, sorry).

[Takashi Iwai]

At Sun, 09 Mar 2003 20:44:35 -0400,
Manuel Jander wrote:
> 
> Oops, i'm very sorry...  wrong list :-(.
> Won't happen again, i swear.
> Please excuse my mistake. Was ment for the OpenVortex devel list.

don't worry :)
i'd like to see the development of ALSA vortex driver.
it would be appreciated if you post the development status to
alsa-devel, too.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

alsa driver

[Brian Furey]

Hi all,
   i'm running the alsa-driver-1.0.0. Im using it with
the OpenH323 application. Packets are transmitted or
received in 32 millisecond intervals or multiples of
32 millisecond intervals.
For example using the G711 codec, packets are
transmitted every 32 milliseconds. For the GSM-06.10
codec, packets are transmitted at alternate intervals
of 64 milliseconds or 96 milliseconds.
Why is this?

Brian.


	
	
		
____________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: alsa driver

[Jaroslav Kysela]

On Tue, 6 Apr 2004, Brian Furey wrote:

> Hi all,
>    i'm running the alsa-driver-1.0.0. Im using it with
> the OpenH323 application. Packets are transmitted or
> received in 32 millisecond intervals or multiples of
> 32 millisecond intervals.
> For example using the G711 codec, packets are
> transmitted every 32 milliseconds. For the GSM-06.10
> codec, packets are transmitted at alternate intervals
> of 64 milliseconds or 96 milliseconds.
> Why is this?

Busy system?

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: alsa driver

[Brian Furey]

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

Jaroslav,
Busy system cant explain something as consequent as this.
When the packet size being transmitted is 30 msecs(240bytes) or 32 msecs(240bytes), the OpenH323 app sends packets every 32 msecs.
 
When the packet size is 80 msecs(132 bytes), the OpenH323 app sends packets at alternate intervals of 64 msecs and 96 msecs.Both are multiples of 32 msecs.
Surely it's to do with the period size being added to the driver sending buffer. The thing is I have got all the info about the period size,no of periods ..etc but it's not adding up yet.
 
Brian.

Jaroslav Kysela <perex@suse.cz> wrote:
On Tue, 6 Apr 2004, Brian Furey wrote:

> Hi all,
> i'm running the alsa-driver-1.0.0. Im using it with
> the OpenH323 application. Packets are transmitted or
> received in 32 millisecond intervals or multiples of
> 32 millisecond intervals.
> For example using the G711 codec, packets are
> transmitted every 32 milliseconds. For the GSM-06.10
> codec, packets are transmitted at alternate intervals
> of 64 milliseconds or 96 milliseconds.
> Why is this?

Busy system?

Jaroslav

-----
Jaroslav Kysela 

Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
		
---------------------------------
  Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now

[-- Attachment #2: Type: text/html, Size: 2393 bytes --]