Re: Z2 Audio info?
> The http://linux.zipitwireless.com/projects/z2kernel describes theYes, I've seen that. I was just wondering if anyone made any
>necessary register setup to initialize audio.
standalone tool to do so yet, I'm a bit lazy to look into actually
coding up said tool :)
>Myself and another engineer from IBM have been looking into writingThat would be great, thanks.
>an audio driver or auto-initializing the registers on OE boot. Will
>let you know if it goes anywhere.
I managed to fix the other issue by setting the block size to 3552
bytes. That made it play mostly error free. (There's still the
occasional loop-glitch) I suspect it has something to do with DMA
based sound output in general, or it's something that the driver isn't
doing, that it's supposed to. It would be great if someone with more
insight could share their opinion on the matter. Is it the best option
to find the magic block size/delay or is there some less ambiguous way
to tell when it's safe to write again, to ensure there's no looping or
--- In email@example.com, Hunter Davis <huntergdavis@...>
>necessary register setup to initialize audio. I assume that you are
> The http://linux.zipitwireless.com/projects/z2kernel describes the
running apps from the zipit environment and not OE, so this may not be
necessary in your case. Myself and another engineer from IBM have
been looking into writing an audio driver or auto-initializing the
registers on OE boot. Will let you know if it goes anywhere.
> From: riddlemoor <t.bone@...>
> To: firstname.lastname@example.org
> Sent: Friday, December 12, 2008 4:18:52 AM
> Subject: [zipitwireless] Z2 Audio info?
> I was wondering if anyone has any experience with Z2 audio?
> For example, does anyone know of a tool that initializes the audio, or
> a mixer by any chance? So far I've only gotten it to work by letting
> the chat app initialize it then killing the process.
> My other problem is somewhat strange. I can cat raw audio data to
> /dev/dsp and it plays fine, but random audio apps that worked fine on
> the Z1 produce broken sound (first second seems ok, but then it plays
> too fast, and when I pause it keeps looping the last block written to
> /dev/dsp) So i'm assuming I'm not doing something I'm supposed to. Do
> I need to query something before writing again, or send some control
> command, or is it because of something else? Modifying the block size
> didn't have much effect on it. Any help would be great. I might decide
> to keep the device around longer if this problem could be fixed.