On Wed, 2003-03-05 at 17:34, Paul Davis wrote:
>
> eh? if it returns any non-zero value, we return from
> hdsp_initialize_firmware() with -EIO, surely?
You're perfectly right, sorry, I've been mixing things up... :)
I guess a reason for it was that getting all those snd_printks from
hdsp_fifo_wa
>On Wed, 2003-03-05 at 15:41, Paul Davis wrote:
>
>> i agree. i can't see why it doesn't, unless the LONG_WAIT delays us
>> for so long that it looks like a freeze ...
>
>It doesn't, as after hitting the magic sysrq sigterm sequence I can see
>the hdsp_fifo_wait's snd_printks appear on a regular ba
On Wed, 2003-03-05 at 15:41, Paul Davis wrote:
> i agree. i can't see why it doesn't, unless the LONG_WAIT delays us
> for so long that it looks like a freeze ...
It doesn't, as after hitting the magic sysrq sigterm sequence I can see
the hdsp_fifo_wait's snd_printks appear on a regular basis (lo
>> OK, so this means that
>>
>> hdsp_fifo_wait (hdsp, 0, some_count);
>>
>> is waiting till the FIFO is empty. by contrast,
>>
>> hdsp_fifo_wait (hdsp, 127, some_count);
>>
>> waits till there is 1 word available in the FIFO, meaning that we can
>> write to it.
>>
>How is that we can
On Wed, 2003-03-05 at 14:38, Paul Davis wrote:
> >in short, i am confused :) :(
>
> but ... help is at hand. i checked my mail archives:
>
> >The fifo status counts the number of words waiting in the FIFO. A value of
> >128 means that the fifo is full. 0 means the fifo is empty.
>
> OK, so this
>in short, i am confused :) :(
but ... help is at hand. i checked my mail archives:
>The fifo status counts the number of words waiting in the FIFO. A value of
>128 means that the fifo is full. 0 means the fifo is empty.
OK, so this means that
hdsp_fifo_wait (hdsp, 0, some_count);
is wait
>If I try to get out of hanged state with the magic sysrq sigterm or
>sigkill sequence, I get a flood of snd_printk messages from the
>hdsp_fifo_wait(...) function in hdsp.c (line 501), with count = 127.
>There are two places where hdsp_fifo_wait is called with count = 127:
>hdsp_write_gain (line 5
On Wed, 2003-03-05 at 10:02, Thomas Charbonnel wrote:
> I'm experiencing complete system lockups with this, in every possible
> situation:
> * cold boot
> * reboot
> * post boot module insertion
>
> I did power off the card after updating, so the firmware has to be
> loaded.
>
> I get no message
On Wed, 2003-03-05 at 00:22, Paul Davis wrote:
> This is a new version of the previous patch, but now also includes:
>
> * use of udelay to force timed loops rather than count-based loops
> * fix hdsp_is_9652()
> * don't include unnecessary playback mixer controls for Multiface
> *
