Re: Hammerfall (hdsp) initialization problem

[Thomas Charbonnel <thomas@undata.org>]

> > that's a known problem with the hdsp driver, a lot of continuous memory
> > has to be allocated, which can more likely be done on a freshly booted
> > machine ...
> > the best solution: keep the cardbus interface plugged into the slot all
> > the time ... if you start the computer, the memory will be allocated
> 
> Actually, I suspect there's more than that. I've tried running a program
> that malloc()'s 1 GB of memory (the amount of RAM I have), writes to it
> and then free()'s it, so there's lots of memory available after that.
> Still doesn't work (and obviously there's lots of continuous memory
> available).
> 
> 	Jean-Marc

The problem is that for the preallocation to work, the card has to be
inserted and recognized (the preallocation code scans for the pci vendor
and device ids), so this is a cardbus specific issue. If the card is not
inserted when the preallocation is run, then it will default at probing
time to the standard snd_dma_alloc_pages which is more and more likely
to fail as your uptime rises. The only solution would be to preallocate
the memory anyway, but most user won't need this. Takashi, how about a
kernel/compile time option forcing preallocation for cardbus hdsp owners
?

Thomas




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click