hdsp driver status

hdsp driver status

[Thomas Charbonnel]

Hi,

To summarize the current problems with the driver :

* there is a locking issue which has been found and solved (thanks again
to Joshua N Pritikin). This was the cause of the freezes Mark and others
have been experiencing. I need to clean the code up before submitting a
patch (hopefully today).

* there is a problem with rev11 firmwares yet to be identified (the
simplest reason could be that the firmware files are wrong)

* the way the matrix mixer is handled for hdsp9652 cards seems wrong.
This could explain the absence of sound output Mark and others are
reporting.

Thomas




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

Re: hdsp driver status

[Jeremy Hall]

Is the locking problem visible in the RME9652 driver as well?

_J

In the new year, Thomas Charbonnel wrote:
> Hi,
> 
> To summarize the current problems with the driver :
> 
> * there is a locking issue which has been found and solved (thanks again
> to Joshua N Pritikin). This was the cause of the freezes Mark and others
> have been experiencing. I need to clean the code up before submitting a
> patch (hopefully today).
> 
> * there is a problem with rev11 firmwares yet to be identified (the
> simplest reason could be that the firmware files are wrong)
> 
> * the way the matrix mixer is handled for hdsp9652 cards seems wrong.
> This could explain the absence of sound output Mark and others are
> reporting.
> 
> Thomas
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 



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

Re: hdsp driver status

[Thomas Charbonnel]

> Is the locking problem visible in the RME9652 driver as well?
> 
> _J

No, or at least not this particular one.

Thomas




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

Re: hdsp driver status

[Paul Davis]

>Is the locking problem visible in the RME9652 driver as well?

no, it has absolutely nothing to do with it. you may as well consider
these entirely different devices. the codebase has very little in
cmmon anymore.

--p


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

Re: hdsp driver status

[Mark Knecht]

Thomas,
   Thanks for the update. It's great to even know that you are actively
looking at it.

   Comments/questions embedded.

Thanks,
Mark

On Mon, 2003-04-14 at 02:55, Thomas Charbonnel wrote:
> Hi,
> 
> To summarize the current problems with the driver :
> 
> * there is a locking issue which has been found and solved (thanks again
> to Joshua N Pritikin). This was the cause of the freezes Mark and others
> have been experiencing. I need to clean the code up before submitting a
> patch (hopefully today).
> 
> * there is a problem with rev11 firmwares yet to be identified (the
> simplest reason could be that the firmware files are wrong)

I noticed that in my post to you yesterday that the Firmware in my card
was listed as 'Revision 1'.


Buffer Size (Latency): 1024 samples (2 periods of 4096 bytes)
Hardware pointer (frames): 0
Passthru: no
Line out: on
Firmware version: 1

Seems a bit strange, but could certainly be correct. Just pointing it
out.

> 
> * the way the matrix mixer is handled for hdsp9652 cards seems wrong.
> This could explain the absence of sound output Mark and others are
> reporting.
> 

I was hoping to hear whether ANY setup of the card was required by the
user to make mixer connections. I had understood (some months ago) that
maybe some 'amixer cset' commands were required to get an older
Hammerfall 9652 to actually output audio. Is this correct? If so, does
the HDSP 9652 require anything similar, as I am doing nothing like that.

Again, if there is anything I can do to help, please let me know.

Thanks,
Mark



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

hdsp driver status

[Paul Davis]

i finally got the information from RME to enable the mixer on the
hdsp-9652. i updated CVS, and the hdsp driver is totally
incompilable. somebody ripped out the definition of HDSP_IO_Type, and
then we have stuff like this:

../../alsa-kernel/pci/rme9652/hdsp.c:403: `HDSP_MATRIX_MIXER_SIZE' undeclared he
re (not in a function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_read_gain':
../../alsa-kernel/pci/rme9652/hdsp.c:655: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
irst use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c:655: (Each undeclared identifier is reporte
d only once
../../alsa-kernel/pci/rme9652/hdsp.c:655: for each function it appears in.)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_write_gain':
../../alsa-kernel/pci/rme9652/hdsp.c:692: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
irst use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_set_defaults':
../../alsa-kernel/pci/rme9652/hdsp.c:3029: `HDSP_MATRIX_MIXER_SIZE' undeclared (
first use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_hwdep_ioctl':
../../alsa-kernel/pci/rme9652/hdsp.c:3729: `hdsp_firmware_t' undeclared (first u
se in this function)
../../alsa-kernel/pci/rme9652/hdsp.c:3729: `firmware' undeclared (first use in t
his

can some fill me in on what is going on? why is the driver so totally broken?


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: hdsp driver status

[Jaroslav Kysela]

On Wed, 7 May 2003, Paul Davis wrote:

> i finally got the information from RME to enable the mixer on the
> hdsp-9652. i updated CVS, and the hdsp driver is totally
> incompilable. somebody ripped out the definition of HDSP_IO_Type, and
> then we have stuff like this:
> 
> ../../alsa-kernel/pci/rme9652/hdsp.c:403: `HDSP_MATRIX_MIXER_SIZE' undeclared he
> re (not in a function)
> ../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_read_gain':
> ../../alsa-kernel/pci/rme9652/hdsp.c:655: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
> irst use in this function)
> ../../alsa-kernel/pci/rme9652/hdsp.c:655: (Each undeclared identifier is reporte
> d only once
> ../../alsa-kernel/pci/rme9652/hdsp.c:655: for each function it appears in.)
> ../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_write_gain':
> ../../alsa-kernel/pci/rme9652/hdsp.c:692: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
> irst use in this function)
> ../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_set_defaults':
> ../../alsa-kernel/pci/rme9652/hdsp.c:3029: `HDSP_MATRIX_MIXER_SIZE' undeclared (
> first use in this function)
> ../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_hwdep_ioctl':
> ../../alsa-kernel/pci/rme9652/hdsp.c:3729: `hdsp_firmware_t' undeclared (first u
> se in this function)
> ../../alsa-kernel/pci/rme9652/hdsp.c:3729: `firmware' undeclared (first use in t
> his
> 
> can some fill me in on what is going on? why is the driver so totally broken?

It's defined in alsa-kernel/include/hdsp.h...

						Jaroslav

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



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: hdsp driver status

[Thomas Charbonnel]

> On Wed, 7 May 2003, Paul Davis wrote:
>
>> somebody ripped out the definition of HDSP_IO_Type, and
>>
> It's defined in alsa-kernel/include/hdsp.h...
>
>

I moved the definition there to make it usable by userspace applications.
I should have warned you about that, sorry.

Thomas





-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

hdsp driver status

[Thomas Charbonnel]

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

Hi,

I've been off the net and busy for a long time. I apologize to anyone
whose mail I didn't answer during this period. I'm slowly catching up with
the huge activity that has been going on this list, focusing on the hdsp
driver issues. I'd like to summarize the driver status :

Fixed :
* Marcus, Jaroslav : thanks for having solved the long (ever ? :)
lasting hdsp midi bug !

Done:
* Takashi : I succesfully tested your memory preallocation patch (only
the hdsp part of it, actually), thanks for it. (Thanks too for the
addition of hdspconf to cvs, it is indeed the latest version).

Remaining:
* HDSP9652: the matrix mixer isn't yet handled right.
* Rev11 + Multiface: either the firmware file is wrong or the io-box
firmware upload scenario has changed for this card revision. Has anyone
ever had success with this combination (or rev11 + Digiface) ?

The attached patch :
* Reenables the hdsp_check_for_iobox function Paul bypassed in his
previous patch. This function is needed for mobile setups. It handles the
cases where the iobox has been unplugged/replugged or lost power supply.
* Fixes the channel limit Mark has reported on the HDSP9652 (24 instead of
26).
* Fixes a locking issue reported by Joshua N Pritikin.

David, Jesse and Patrick, I'm back at work on the totalmix clone. It
should be out for testing really soon. Sorry for having been so
unresponsive lately.

Thomas



[-- Attachment #2: hdsp-03-07-03.patch --]
[-- Type: application/octet-stream, Size: 2391 bytes --]

--- hdsp.c.old	2003-07-03 12:23:52.000000000 +0200
+++ hdsp.c	2003-07-03 12:24:07.000000000 +0200
@@ -76,8 +76,8 @@
 #define DIGIFACE_DS_CHANNELS     14
 #define MULTIFACE_SS_CHANNELS    18
 #define MULTIFACE_DS_CHANNELS    14
-#define H9652_DS_CHANNELS        24
-#define H9652_SS_CHANNELS        24
+#define H9652_DS_CHANNELS        26
+#define H9652_SS_CHANNELS        14
 
 /* Write registers. These are defined as byte-offsets from the iobase value.
  */
@@ -497,15 +497,15 @@
 
 static inline int hdsp_check_for_iobox (hdsp_t *hdsp)
 {
-	return 0;
-#if 0
+
+	if (hdsp->io_type == H9652) return 0;
 	if (hdsp_read (hdsp, HDSP_statusRegister) & HDSP_ConfigError) {
 		snd_printk ("Hammerfall-DSP: no Digiface or Multiface connected!\n");
 		hdsp->state &= ~HDSP_FirmwareLoaded;
 		return -EIO;
 	}
 	return 0;
-#endif
+
 }
 
 static int snd_hdsp_load_firmware_from_cache(hdsp_t *hdsp) {
@@ -835,6 +835,11 @@
 	int current_rate;
 	int rate_bits;
 
+	/* ASSUMPTION: hdsp->lock is either help, or
+	   there is no need for it (e.g. during module
+	   initialization).
+	*/
+	
 	if (!(hdsp->control_register & HDSP_ClockModeMaster)) {	
 		if (called_internally) {
 			/* request from ctl or card initialization */
@@ -866,8 +871,6 @@
 	   exists for externally-driven rate changes. All we can do
 	   is to flag rate changes in the read/write routines.  */
 
-	spin_lock_irq(&hdsp->lock);
-
 	switch (rate) {
 	case 32000:
 		if (current_rate > 48000) {
@@ -906,7 +909,6 @@
 		rate_bits = HDSP_Frequency96KHz;
 		break;
 	default:
-		spin_unlock_irq(&hdsp->lock);
 		return -EINVAL;
 	}
 
@@ -914,7 +916,6 @@
 		snd_printk ("cannot change between single- and double-speed mode (capture PID = %d, playback PID = %d)\n",
 			    hdsp->capture_pid,
 			    hdsp->playback_pid);
-		spin_unlock_irq(&hdsp->lock);
 		return -EBUSY;
 	}
 
@@ -945,7 +946,6 @@
 		hdsp_update_simple_mixer_controls (hdsp);
 	}
 
-	spin_unlock_irq(&hdsp->lock);
 	return 0;
 }
 
@@ -3346,9 +3346,13 @@
 	/* how to make sure that the rate matches an externally-set one ?
 	 */
 
+	spin_lock_irq(&hdsp->lock);
 	if ((err = hdsp_set_rate(hdsp, params_rate(params), 0)) < 0) {
+		spin_unlock_irq(&hdsp->lock);
 		_snd_pcm_hw_param_setempty(params, SNDRV_PCM_HW_PARAM_RATE);
 		return err;
+	} else {
+		spin_unlock_irq(&hdsp->lock);
 	}
 
 	if ((err = hdsp_set_interrupt_interval(hdsp, params_period_size(params))) < 0) {

Re: hdsp driver status

[Takashi Iwai]

Hi Thomas,

good to hear you again!

At Thu, 3 Jul 2003 13:12:54 +0200 (CEST),
Thomas Charbonnel wrote:
>
> Done:
> * Takashi : I succesfully tested your memory preallocation patch (only
> the hdsp part of it, actually), thanks for it. (Thanks too for the
> addition of hdspconf to cvs, it is indeed the latest version).

ok, i committed my last patch to cvs now.
if it worked on hdsp, it must work on rme9652 basically.

> Remaining:
> * HDSP9652: the matrix mixer isn't yet handled right.

do you have plan to do this for totalmix?


> The attached patch :
> * Reenables the hdsp_check_for_iobox function Paul bypassed in his
> previous patch. This function is needed for mobile setups. It handles the
> cases where the iobox has been unplugged/replugged or lost power supply.
> * Fixes the channel limit Mark has reported on the HDSP9652 (24 instead of
> 26).
> * Fixes a locking issue reported by Joshua N Pritikin.

applied.  thanks!


ciao,

Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

RE: hdsp driver status

[Mark Knecht]

Thomas,
   Great to have you back! Looking forward to the matrix mixer actually
working one of these days. I hope you can work it into your design
somewhere.

Thanks,
Mark

> -----Original Message-----
> From: alsa-devel-admin@lists.sourceforge.net
> [mailto:alsa-devel-admin@lists.sourceforge.net]On Behalf Of Thomas
> Charbonnel
> Sent: Thursday, July 03, 2003 4:13 AM
> To: alsa-devel@lists.sourceforge.net
> Subject: [Alsa-devel] hdsp driver status
>
>
> Hi,
>
> I've been off the net and busy for a long time. I apologize to anyone
> whose mail I didn't answer during this period. I'm slowly catching up with
> the huge activity that has been going on this list, focusing on the hdsp
> driver issues. I'd like to summarize the driver status :
>
> Fixed :
> * Marcus, Jaroslav : thanks for having solved the long (ever ? :)
> lasting hdsp midi bug !
>
> Done:
> * Takashi : I succesfully tested your memory preallocation patch (only
> the hdsp part of it, actually), thanks for it. (Thanks too for the
> addition of hdspconf to cvs, it is indeed the latest version).
>
> Remaining:
> * HDSP9652: the matrix mixer isn't yet handled right.
> * Rev11 + Multiface: either the firmware file is wrong or the io-box
> firmware upload scenario has changed for this card revision. Has anyone
> ever had success with this combination (or rev11 + Digiface) ?
>
> The attached patch :
> * Reenables the hdsp_check_for_iobox function Paul bypassed in his
> previous patch. This function is needed for mobile setups. It handles the
> cases where the iobox has been unplugged/replugged or lost power supply.
> * Fixes the channel limit Mark has reported on the HDSP9652 (24 instead of
> 26).
> * Fixes a locking issue reported by Joshua N Pritikin.
>
> David, Jesse and Patrick, I'm back at work on the totalmix clone. It
> should be out for testing really soon. Sorry for having been so
> unresponsive lately.
>
> Thomas
>
>
>




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Patrick Shirkey]

Thomas Charbonnel wrote:
> 
> Remaining:
> * HDSP9652: the matrix mixer isn't yet handled right.
> * Rev11 + Multiface: either the firmware file is wrong or the io-box
> firmware upload scenario has changed for this card revision. Has anyone
> ever had success with this combination (or rev11 + Digiface) ?
> 

I am using multiface which hasn't been flashed. I have upgraded to a 
newer kernel (2.4.21) (0.9.4 tarball) and now I don't get the error 
about finding hwdep when I run hdsploader but there is still no sound 
coming from the device.

My friend tells me that in windows it will always have the WC button on 
when it is working correctly.

In this case after running hdsploader the box flashes and then all the 
lights turn off.

This device has worked with older versions of the alsa drivers.




-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Patrick Shirkey]

Patrick Shirkey wrote:
> Thomas Charbonnel wrote:
> 
>>
>> Remaining:
>> * HDSP9652: the matrix mixer isn't yet handled right.
>> * Rev11 + Multiface: either the firmware file is wrong or the io-box
>> firmware upload scenario has changed for this card revision. Has anyone
>> ever had success with this combination (or rev11 + Digiface) ?
>>
> 
> I am using multiface which hasn't been flashed. I have upgraded to a 
> newer kernel (2.4.21) (0.9.4 tarball) and now I don't get the error 
> about finding hwdep when I run hdsploader but there is still no sound 
> coming from the device.
> 
> My friend tells me that in windows it will always have the WC button on 
> when it is working correctly.
> 
> In this case after running hdsploader the box flashes and then all the 
> lights turn off.
> 
> This device has worked with older versions of the alsa drivers.
> 

following the above I decided to check I was setting the correct params 
in the matrix and it turns out that line out has been moved to numid 22 
(before it was 5).

amixer -D hw:1 cset numid=22 0,0,16384

"And out of the box came a burbling noise, white noise that is, RME gold..."

So Jed wasn't rich yet but he was almost there. At least we know that 
the latest revisions are almost functional. I tried playing a very loud 
tune and I can just make it out if I listen carefully. I also tried 
using a volume of 32768 but there was no change in the levels I could hear.

Am I right to use alsamixer to set the volume for outputs 1-8?

I'll also try with amixer just incase.


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Patrick Shirkey]

Patrick Shirkey wrote:
> 
> I'll also try with amixer just incase.

Yep. Things changed again. This time Jeds rich and I'm happy.

The line outs are still kaput but the outputs are working.

I got a nice clear clean signal from output 1 and 2 after running:

amixer -c 1 cset numid=23 0,0,4000;
amixer -c 1 cset numid=24 0,0,4000;
amixer -c 1 cset numid=25 0,0,4000;
amixer -c 1 cset numid=26 0,0,4000;
amixer -c 1 cset numid=27 0,0,4000;
amixer -c 1 cset numid=28 0,0,4000;
amixer -c 1 cset numid=29 0,0,4000;
amixer -c 1 cset numid=30 0,0,4000;
amixer -c 1 cset numid=31 0,0,4000;
amixer -c 1 cset numid=32 0,0,4000;
amixer -c 1 cset numid=33 0,0,4000;
amixer -c 1 cset numid=34 0,0,4000;
amixer -c 1 cset numid=34 0,0,4000;
amixer -c 1 cset numid=35 0,0,4000;
amixer -c 1 cset numid=36 0,0,4000;
amixer -c 1 cset numid=37 0,0,4000;
amixer -c 1 cset numid=38 0,0,4000;
amixer -c 1 cset numid=39 0,0,4000;
amixer -c 1 cset numid=40 0,0,4000;

Someone might want to make a script out of this...

Now I can start recording :)

-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Patrick Shirkey]

Patrick Shirkey wrote:
> Patrick Shirkey wrote:
> 
>>
>> I'll also try with amixer just incase.
> 
> 
> Yep. Things changed again. This time Jeds rich and I'm happy.
> 
> The line outs are still kaput but the outputs are working.
> 
> I got a nice clear clean signal from output 1 and 2 after running:
> 

One more addition. After doing this I have to adjust the level in 
alsamixer before I can hear the sound.

Kind of odd. amixer will do it's thing happily but alsamixer thinks 
everything is still mute.


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Justin Cormack]

On Thu, 2003-07-03 at 17:15, Patrick Shirkey wrote:
> Patrick Shirkey wrote:
> > Thomas Charbonnel wrote:
> > 
> >>
> >> Remaining:
> >> * HDSP9652: the matrix mixer isn't yet handled right.
> >> * Rev11 + Multiface: either the firmware file is wrong or the io-box
> >> firmware upload scenario has changed for this card revision. Has anyone
> >> ever had success with this combination (or rev11 + Digiface) ?
> >>

you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
0.9.4/todays cvs.

And now I have a 0xa revision that wont work at all on any version of
the driver...


Justin




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[jfm3]

On Thu, 2003-07-03 at 13:08, Justin Cormack wrote:
> On Thu, 2003-07-03 at 17:15, Patrick Shirkey wrote:
> > Patrick Shirkey wrote:
> > > Thomas Charbonnel wrote:
> > > 
> > >>
> > >> Remaining:
> > >> * HDSP9652: the matrix mixer isn't yet handled right.
> > >> * Rev11 + Multiface: either the firmware file is wrong or the io-box
> > >> firmware upload scenario has changed for this card revision. Has anyone
> > >> ever had success with this combination (or rev11 + Digiface) ?
> > >>
> 
> you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
> 0.9.4/todays cvs.
> 
> And now I have a 0xa revision that wont work at all on any version of
> the driver...

I have an 0xb Multiface. I haven't been able to load the firmware with
0.9.4, either with the PCI or the PCMCIA interface. I have not tried
0.9.0rc5, nor have I tried loading the firmware with windows and warm
booting. Either route is a lot of work. I'd rather see the hardware
documentation and work on the driver source code. Thanks for any help!

-- 
(jfm3  2838 BCBA 93BA 3058 ED95  A42C 37DB 66D1 B43C 9FD0)



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Patrick Shirkey]

jfm3 wrote:
> On Thu, 2003-07-03 at 13:08, Justin Cormack wrote:
> 
>>On Thu, 2003-07-03 at 17:15, Patrick Shirkey wrote:
>>
>>>Patrick Shirkey wrote:
>>>
>>>>Thomas Charbonnel wrote:
>>>>
>>>>
>>>>>Remaining:
>>>>>* HDSP9652: the matrix mixer isn't yet handled right.
>>>>>* Rev11 + Multiface: either the firmware file is wrong or the io-box
>>>>>firmware upload scenario has changed for this card revision. Has anyone
>>>>>ever had success with this combination (or rev11 + Digiface) ?
>>>>>
>>>>
>>you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
>>0.9.4/todays cvs.
>>
>>And now I have a 0xa revision that wont work at all on any version of
>>the driver...
> 
> 
> I have an 0xb Multiface. I haven't been able to load the firmware with
> 0.9.4, either with the PCI or the PCMCIA interface. I have not tried
> 0.9.0rc5, nor have I tried loading the firmware with windows and warm
> booting. Either route is a lot of work. I'd rather see the hardware
> documentation and work on the driver source code. Thanks for any help!
> 

Try using this script if you don't already have something similar. I now 
get sound through my line out:

--------------
modprobe snd-hdsp; hdsploader;

# route jack inputs to line out
# left
amixer -c 1 cset numid=5 26,26,4000
amixer -c 1 cset numid=5 28,26,4000
amixer -c 1 cset numid=5 30,26,4000
amixer -c 1 cset numid=5 32,26,4000
# right
amixer -c 1 cset numid=5 27,27,4000
amixer -c 1 cset numid=5 29,27,4000
amixer -c 1 cset numid=5 31,27,4000
amixer -c 1 cset numid=5 33,27,4000

# Set volume for analog outputs to reasonable level
# and connect jack inputs to analog outs
amixer -c 1 cset numid=5 26,0,4000;
amixer -c 1 cset numid=5 27,1,4000;
amixer -c 1 cset numid=5 28,2,4000;
amixer -c 1 cset numid=5 29,3,4000;
amixer -c 1 cset numid=5 30,4,4000;
amixer -c 1 cset numid=5 31,5,4000;
amixer -c 1 cset numid=5 32,6,4000;
amixer -c 1 cset numid=5 33,7,4000;
amixer -c 1 cset numid=5 34,8,4000;
-------------

-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

> following the above I decided to check I was setting the correct params
> in the matrix and it turns out that line out has been moved to numid 22
> (before it was 5).
>
> amixer -D hw:1 cset numid=22 0,0,16384
>

You're mixing things up.
This is the syntax of the matrix mixer ctl.
The line out value type is boolean. To enable line outs you should this :
amixer -D hw:1 cset numid=22 1

I think the command you were using was doing the exact opposite of what
you wanted.

Maybe you should remove your asound.state file. Alsactl may try to restore
the state of parameters whose numid changed, leading to unpredicted and
presumably unwanted results.

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

>> >> Remaining:
>> >> * HDSP9652: the matrix mixer isn't yet handled right.
>> >> * Rev11 + Multiface: either the firmware file is wrong or the
>> io-box firmware upload scenario has changed for this card revision.
>> Has anyone ever had success with this combination (or rev11 +
>> Digiface) ?
>> >>
>
> you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
> 0.9.4/todays cvs.

That's surprising. Does the matrix mixer work with 0.9.0rc5 ?

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[jfm3]

On Thu, 2003-07-03 at 14:57, Patrick Shirkey wrote:
> > I have an 0xb Multiface. I haven't been able to load the firmware with
> > 0.9.4, either with the PCI or the PCMCIA interface. [...]
> 
> Try using this script if you don't already have something similar. I now 
> get sound through my line out:
> 
> --------------
> modprobe snd-hdsp; hdsploader;
> 
> # route jack inputs to line out
> # left
> amixer -c 1 cset numid=5 26,26,4000
> amixer -c 1 cset numid=5 28,26,4000 [...]

Thanks for the script. My problem isn't getting amixer commands right, I
don't even get that far. As my original message said, I can't load the
firmware. hdsploader fails. I don't have the output of how it fails with
me, but I've posted it to alsa-devel before.
-- 
(jfm3  2838 BCBA 93BA 3058 ED95  A42C 37DB 66D1 B43C 9FD0)



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

>
> I have an 0xb Multiface. I haven't been able to load the firmware with
> 0.9.4, either with the PCI or the PCMCIA interface. I have not tried
> 0.9.0rc5, nor have I tried loading the firmware with windows and warm
> booting. Either route is a lot of work. I'd rather see the hardware
> documentation and work on the driver source code. Thanks for any help!
>

The documentation is the driver code. Paul is in contact with people from
RME. As of today I'm not, but I'll try to contact them. I'd be as happy as
you to see the driver working smoothly in all possible configurations.

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

RE: hdsp driver status

[Mark Knecht]

>
> The documentation is the driver code. Paul is in contact with people from
> RME. As of today I'm not, but I'll try to contact them. I'd be as happy as
> you to see the driver working smoothly in all possible configurations.
>
> Thomas
>

Thomas,
   We RME users are very happy to have you on our side!

   Can you give some insight (if you have enough info to comment!) into how
much of the driver for the HDSP/DF/MF is also used for the HDSP 9652? I'm
sort of concerned that after 6 months of no mixer on the HDSP 9652, the
DF/MF mixer will get fixed, and then I'll find out it has nothing to do the
HDSP 9652 and be let down again.

   Is it one common design, or is the mixer different?

Thanks,
Mark




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

RE: hdsp driver status

[Thomas Charbonnel]

> I'm sort of concerned that after 6 months of no mixer on the HDSP 9652,
> the DF/MF mixer will get fixed, and then I'll find out it has nothing to
> do the HDSP 9652 and be let down again.
>

The MF/DF mixer works, but firmware upload to the iobox fails with some
card revision. On the HDSP 9652 no firmware has to be uploaded (hdsploader
is unecessary), but the mixer is broken.

>    Is it one common design, or is the mixer different?

It is one common design BUT the mixer is different...

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

RE: hdsp driver status

[Mark Knecht]

On Thu, 2003-07-03 at 18:20, Thomas Charbonnel wrote:
> > I'm sort of concerned that after 6 months of no mixer on the HDSP 9652,
> > the DF/MF mixer will get fixed, and then I'll find out it has nothing to
> > do the HDSP 9652 and be let down again.
> >
> 
> The MF/DF mixer works, but firmware upload to the iobox fails with some
> card revision. On the HDSP 9652 no firmware has to be uploaded (hdsploader
> is unecessary), but the mixer is broken.
> 
> >    Is it one common design, or is the mixer different?
> 
> It is one common design BUT the mixer is different...
> 
> Thomas
> 
Thanks for the description.

I've written the next paragraph 5 times, but just don't want to do this
all over again.

Anyone wanna buy an HDSP 9652 cheap?

Bye,
Mark



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Justin Cormack]

On Thu, 2003-07-03 at 21:15, Thomas Charbonnel wrote:
> >> >> Remaining:
> >> >> * HDSP9652: the matrix mixer isn't yet handled right.
> >> >> * Rev11 + Multiface: either the firmware file is wrong or the
> >> io-box firmware upload scenario has changed for this card revision.
> >> Has anyone ever had success with this combination (or rev11 +
> >> Digiface) ?
> >> >>
> >
> > you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
> > 0.9.4/todays cvs.
> 
> That's surprising. Does the matrix mixer work with 0.9.0rc5 ?

Yes its fine. But I though it was only the 9652 that had a matrix mixer
problem...

Justin




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

>> > you mean 0xb? I have one that works on 0.9.0rc5, but wont work on
>> 0.9.4/todays cvs.
>>
>> That's surprising. Does the matrix mixer work with 0.9.0rc5 ?
>
> Yes its fine. But I though it was only the 9652 that had a matrix mixer
> problem...
>
> Justin
>

I've just had a look at the 0.9.0rc5 driver code. Either your card is not
a 0xb version, either you're using a patched 0.9.0rc5:

(from the snd_hdsp_create() function)

        switch (rev & 0xff) {
        case 0xa:
                /* hdsp_initialize_firmware() will reset this */
                hdsp->card_name = "RME Hammerfall DSP";
                break;

        default:
                return -ENODEV;
        }



If you patched your driver (e.g. adding a 0xb case to the rev switch) then
this means the rev 0xb cards can work with the old firmware, which
surprises me a lot. I remember trying once a rev 0xb card a couple of
months ago. I used it in combination with my 0xa card to test Adat and
S/PDIF external sync. I forced it to initialize with the old firmware, but
IIRC the matrix mixer was broken.

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Justin Cormack]

On Fri, 2003-07-04 at 14:58, Thomas Charbonnel wrote:
> > And the driver is 0.9.0rc6 not 5, and it is patched to add 0xb (unless
> > that was in 0.9.0rc6 but not 5). And the matrix mixer does work (just
> > rechecked, which took a little while as the machine is in another
> > country...)
> 
> Ok, thanks for your help. Could you then try the latest driver with this
> patch applied to hdsploader. It forces the upload of the true and tested
> old firmware. What bothers me is that if RME insists so much on flashing
> the cards when upgrading driver, it must be that something changes in the
> way the hardware is accessed. I remember something was broken when I tried
> the 0xb card, but can't remember what. It could be the metering stuff I
> was debugging then. At that time we were waiting for the new firmware
> files from RME, and I expected it would solve the problem.

ok, will try on Monday/Tuesday when I am in same country as the card as
it is easier. I have a 0xa here that I will test over the weekend.

> Did you drop the alsa-dev CC on purpose ?

No, accident...



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[jfm3]

> On Fri, 2003-07-04 at 14:58, Thomas Charbonnel wrote:
>> > And the driver is 0.9.0rc6 not 5, and it is patched to add 0xb
>> (unless that was in 0.9.0rc6 but not 5). And the matrix mixer does
>> work (just rechecked, which took a little while as the machine is in
>> another country...)
>>
>> Ok, thanks for your help. Could you then try the latest driver with
>> this patch applied to hdsploader. It forces the upload of the true and
>> tested old firmware. What bothers me is that if RME insists so much on
>> flashing the cards when upgrading driver, it must be that something
>> changes in the way the hardware is accessed. I remember something was
>> broken when I tried the 0xb card, but can't remember what. It could be
>> the metering stuff I was debugging then. At that time we were waiting
>> for the new firmware files from RME, and I expected it would solve the
>> problem.
>
> ok, will try on Monday/Tuesday when I am in same country as the card as
> it is easier. I have a 0xa here that I will test over the weekend.
>
>> Did you drop the alsa-dev CC on purpose ?
>
> No, accident...
>

I would like to give this patch a go. Can you post it to the list? (Or did
I miss it somehow?)

(jfm3)




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

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

>
>>> Did you drop the alsa-dev CC on purpose ?
>>
>> No, accident...
>>
>
> I would like to give this patch a go. Can you post it to the list? (Or
> did I miss it somehow?)
>
>

Sorry, it did't get copied. Here it is.

Thomas



[-- Attachment #2: hdsploader.patch --]
[-- Type: application/octet-stream, Size: 401 bytes --]

--- hdsploader.c.old	2003-07-04 15:33:34.000000000 +0200
+++ hdsploader.c	2003-07-04 15:34:35.000000000 +0200
@@ -59,11 +59,7 @@
     
     switch (version.io_type) {
     case Multiface:
-	if (version.firmware_rev == 0xa) {
-	    fw = multiface_firmware;
-	} else {
-	    fw = multiface_firmware_rev11;
-	}
+	fw = multiface_firmware;
 	break;
     case Digiface:
 	if (version.firmware_rev == 0xa) {

Re: hdsp driver status

[jfm3]

That hdsploader patch sort of works. I can get sound out of my Multiface now.

I ran hdsploader the first time and it failed. I ran it a second time and
the red light on the Multiface went out, but the hdsploader process never
finished. In fact, it did not even respond to kill -9. It was idle --
neither user nor kernel cpus were being used by it as it wedged. But the
red light on the Multiface was out. So I rebooted Linux, running
hdsploader now works, and now I can hear sound out of the Multiface.

I still have no idea what I'm doing in terms of managing that gigantic
mixer. My modules.conf file needs work. Let me see if I can narrow down
the problem some more, or blame it on cosmic rays, or something.

Much thanks to all.

(jfm3)




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[jfm3]

> I ran hdsploader the first time and it failed. I ran it a second time
> and the red light on the Multiface went out, [...]

For the record, this is incorrect. I run it once and the red light goes
out. I have a feeling the error message is incorrect, because the "card"
seems to work now. hdsploader seems to not be robust in the face of
running twice against the same card. Again, thank you.

(jfm3)




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Thomas Charbonnel]

>
>> I ran hdsploader the first time and it failed. I ran it a second time
>> and the red light on the Multiface went out, [...]
>
> For the record, this is incorrect. I run it once and the red light goes
> out. I have a feeling the error message is incorrect, because the "card"
> seems to work now. hdsploader seems to not be robust in the face of
> running twice against the same card. Again, thank you.
>

Thanks for your report. I'm glad the card gets of some use for rev 11
multiface users, but note that this is more of a workaround than the real
solution. I really suspect something is broken when using the old firmware
with rev 11 cards.
Can you please send me the output of dmesg just after you run hdsploader
and it returns an error, and report precisely the status of the card
before and after hdsploader is run (red light on/off, sound working or
not) ?

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: hdsp driver status

[Jesse Chappell]

Thomas Charbonnel wrote on Sun, 06-Jul-2003:

 > >
 > >> I ran hdsploader the first time and it failed. I ran it a second time
 > >> and the red light on the Multiface went out, [...]
 > >
 > > For the record, this is incorrect. I run it once and the red light goes
 > > out. I have a feeling the error message is incorrect, because the "card"
 > > seems to work now. hdsploader seems to not be robust in the face of
 > > running twice against the same card. Again, thank you.
 > >
 > 
 > Thanks for your report. I'm glad the card gets of some use for rev 11
 > multiface users, but note that this is more of a workaround than the real
 > solution. I really suspect something is broken when using the old firmware
 > with rev 11 cards.
 > Can you please send me the output of dmesg just after you run hdsploader
 > and it returns an error, and report precisely the status of the card
 > before and after hdsploader is run (red light on/off, sound working or
 > not) ?
 
OK, I too tried your patch (I have cardbus/multiface rev 0xb)
and the red light *did* go out but gave the following error
message:

 hdsploader - firmware loader for RME Hammerfall DSP cards
 Looking for HDSP + Multiface or Digiface cards :
 Card 0 : Intel 82801CA-ICH3 at 0x1c00, irq 9
 Card 1 : RME Hammerfall DSP at 0x31000000, irq 9
 Upload firmware for card hw:1
 Hwdep ioctl error on card hw:1 : Input/output error.

Here is what dmesg reports:

ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 0 failed after 30 iterations
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:3804: initializing firmware upload
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:522: loading firmware
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:644: wait for FIFO status <= 0 failed after 5000 iterations
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:543: timeout at end of firmware loading

However, due to that timeout, initialization didn't complete and
there is nothing in /proc/asound/card1/ except id.

I then ran it again:
$ hdsploader
hdsploader - firmware loader for RME Hammerfall DSP cards
Looking for HDSP + Multiface or Digiface cards :
Card 0 : Intel 82801CA-ICH3 at 0x1c00, irq 9
Card 1 : RME Hammerfall DSP at 0x31000000, irq 9
Upload firmware for card hw:1
Firmware uploaded for card hw:1

dmesg reports (the extra debugging line was added by me to the
kernel driver):
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:3804: initializing firmware upload
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:3969: got past proc init stuff
ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:3037: sending all inputs and playback streams to line outs.

At this point everything looks good in /proc/asound/card1/hdsp:

$ cat /proc/asound/card1/hdsp
RME Hammerfall DSP + Multiface (Card #2)
Buffers: capture c0e00000 playback c0c00000
IRQ: 9 Registers bus: 0x31000000 VM: 0xf0a32000
Control register: 0x10080de
Status register: 0x12000000
Status2 register: 0xffff0703
FIFO status: 0
MIDI1 Output status: 0xffffff00
MIDI1 Input status: 0xffffff00
MIDI2 Output status: 0xffffff00
MIDI2 Input status: 0xffffff00

Buffer Size (Latency): 8192 samples (2 periods of 32768 bytes)
Hardware pointer (frames): 0
Passthru: no
Line out: on
Firmware version: 5

Sample Clock Source: Internal 48 kHz
Preferred Sync Reference: ADAT1
AutoSync Reference: None
AutoSync Frequency: 0
System Clock Mode: Master
System Clock Frequency: 48000

IEC958 input: Internal
IEC958 output: Coaxial only
IEC958 quality: Consumer
IEC958 emphasis: off
IEC958 NonAudio: off
IEC958 sample rate: Error flag set

ADAT1: No Lock
SPDIF: No Lock
Word Clock: No Lock
ADAT Sync: No Lock

==============================================================

I can use amixer to set up things as per usual, and jack starts
normally.  However, I get no sound whatsoever.  

Loading the firmware via Windows, rebooting, and setting up the card
identically with amixer *does* yield sound.

So it looks like some critical parts for proper communication
to the multiface need the proper firmware to work with the rev
0xb interface. 

Back to trying to load the proper rev11 firmware, it looks like
some part of the communication protocol must have changed, or
the multiface_firmware_rev11.dat is corrupt.  I wonder if there
is any way to verify it.  

jlc


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps

Re: hdsp driver status

[Thomas Charbonnel]

> I can use amixer to set up things as per usual, and jack starts
> normally.  However, I get no sound whatsoever.
>
> Loading the firmware via Windows, rebooting, and setting up the card
> identically with amixer *does* yield sound.
>
> So it looks like some critical parts for proper communication
> to the multiface need the proper firmware to work with the rev
> 0xb interface.
>
> Back to trying to load the proper rev11 firmware, it looks like
> some part of the communication protocol must have changed, or
> the multiface_firmware_rev11.dat is corrupt.  I wonder if there
> is any way to verify it.
>
> jlc

I did exactly the same test yesterday on a friend's rev 11 card. In fact
there is sound, but all messed up. I got sound on output 3 from
playback_15, on output 12 from playback_11, on output 9 from playback_3. I
could check too that strictly nothing happens with the new firmware, which
leads me to same conclusions. I'm trying to contact RME on this issue, the
problem being I do not have Paul's contact address. I sent a mail
yesterday to Matthias Carstens who's well known to all RME forum readers
and I'm waiting for an answer.

Thomas





-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps