[alsa-devel] [PATCH 3/5] asihpi: Remove HPI4000

Eliot Blennerhassett linux at audioscience.com
Thu Mar 13 21:46:02 CET 2008

Takashi Iwai wrote:
> At Fri, 07 Mar 2008 12:32:52 +1300,
> Eliot Blennerhassett wrote:
>> On Thursday 06 March 2008 14:49:18 Eliot Blennerhassett wrote:
>>> Remove HPI4000
>> This also requires update to alsa-firmware/asihpi with files from 
>> http://audioscience.com/internet/download/firmware/dspbins30914.tar.gz
>> dsp4*.bin are no longer required.
> Oops, forgot to update this -- committed to HG tree now.


>> Also alsa-driver/pci/asihpi/hpi4000.* are no longer required.
>> AudioScience next stable driver release (3.10.0) will not include support for 
>> ASI4xxx cards.
>> AudioScience will continue to maintain our version 3.08.xx with bugfixes for 
>> these cards and  ALSA 1.0.16 will be the last alsa release with support for 
>> ASI4xxx.

> OK.  BTW, what if the newer firmware is loaded onto the old driver?

Within limits (how far apart driver and firmware are) this will work. 
Mostly we are adding functions to the firmware, so old driver will work 
with new firmware but a new driver won't work with old firmware.
Sometimes old functions are deprecated, but we don't remove them 
straight away.

In the windows world our "driver" install includes driver, firmware, 
userspace dll, python bindings, and mixer application all matching.

> Would it be safer to rename the firmware file for each incompatible
> version?  If yes, we can change the asihpi driver code together with
> the firmware renames to couple tightly.

The firmware images contain the HPI version encoded in the header.  I 
will at least log a warning that the driver and firmware version do not 

I guess its possible to use versioned file names. Did you have something 
in mind? Currently the filename is generated from an adapter ID:

sprintf(fw_name, "asihpi/dsp%04x.bin", nAdapter);



More information about the Alsa-devel mailing list