Re: Re: Echo driver

Re: Re: Echo driver

[Yon Mercury]

Giuliano,

I ran System Explorer on the Ricoh Bridge (Echo card was plugged in and 
working) and it produced the registers in a table format:

  __ Device __     CardBus Bridge
                                                                              
                                                                              
  00 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F   Refresh    : ON        
  00 80 11 76 04 07 00 10 02 80 00 07 06 00 40 82 00                          
  10 00 00 00 00 DC 00 00 02 00 02 02 B0 00 00 10 0C   Rev ID        : 80     
  20 00 F0 1F 0C 00 00 00 00 00 00 00 00 FC FF 00 00   Int Line (IRQ): 0A     
  30 00 00 00 00 00 00 00 00 00 00 00 00 0A 01 00 04   Int Pin       : 01     
  40 CF 10 9A 10 01 00 00 00 00 00 00 00 00 00 00 00   Latency Timer : 40     
  50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Sub.Vendor ID : FFFC   
  60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Subsystem ID  : 0000   
  70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00                          
  80 00 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30   #0: 00000000 FFFFF000  
  90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #1: 020000DC 020000DC  
  A0 00 00 00 00 00 00 00 00 00 00 0F 00 00 00 00 00   #2: B0020200 F8FFFFFF  
  B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #3: 0C100000 FFFFF000  
  C0 CF 10 9A 10 00 00 00 00 00 00 00 00 00 00 00 00   #4: 0C1FF000 FFFFF000  
  D0 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 FE   #5: 00000000 FFFFF000  
  E0 00 C0 C0 24 00 00 00 00 00 00 00 00 00 00 00 00                          
  F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ROM: 00000000          
                                                                              
  Type: PCI        Bus: 00  Device: 0F  Function: 00                          
  Type value to modify.                                                       

  __ Device __     CardBus Bridge


  30 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F   Refresh    : ON
  00 80 11 76 04 07 00 10 02 80 00 07 06 00 40 82 00
  10 00 10 00 0C DC 00 00 02 00 03 03 B0 00 F0 FF FF   Rev ID        : 80
  20 00 00 00 00 00 F0 FF FF 00 00 00 00 FC FF FF FF   Int Line (IRQ): 0A
  30 00 00 00 00 FC FF 00 00 00 00 00 00 0A 02 80 04   Int Pin       : 02
  40 CF 10 9A 10 01 00 00 00 00 00 00 00 00 00 00 00   Latency Timer : 40
  50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Sub.Vendor ID : FFFC
  60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Subsystem ID  : FFFF
  70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  80 00 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30   #0: 0C001000 FFFFF000
  90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #1: 020000DC 020000DC
  A0 00 00 00 00 00 00 00 00 00 00 0F 00 00 00 00 00   #2: B0030300 F8FFFFFF
  B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #3: FFFFF000 FFFFF000
  C0 CF 10 9A 10 00 00 00 00 00 00 00 00 00 00 00 00   #4: 00000000 FFFFF000
  D0 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 FE   #5: FFFFF000 FFFFF000
  E0 00 40 C0 24 00 00 00 00 00 00 00 00 00 00 00 00
  F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ROM: 00000000

  Type: PCI        Bus: 00  Device: 0F  Function: 01

Paul Davis mentioned on one of the lists that it's possible to get/set the 
CardBus registers using lspci/setpci. I will have a look.

On Mon, 22 Nov 2004 17:29:23 +0100 (CET), Giuliano Pochini wrote
> I wrote to one of the people that had a similar problems
> some time ago with a RME card. He sent me the attached
> program. It should display the cardbus registers setting
> under windos. We can try to copy it under Linux, maybe
> it works. I also found some infos about the bridge chip.
> It has some custom registers that may need a proper
> setting.
> 
> --
> Giuliano.





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo driver

[Yon Mercury]

Giuliano,

OK, here's a comparison of the CardBus registers between Linux and Windows.
As you can see, some registers are different-- take 0D for example.

The question is, what registers are likely to be the ones we have to change?

Linux
-----

localhost:~# lspci -s 00:0f.0 -xxx
0000:00:0f.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
00: 80 11 76 04 07 00 10 02 80 00 07 06 00 a8 82 00
10: 00 00 00 10 dc 00 00 22 00 02 05 b0 00 00 40 10
20: 00 f0 7f 10 00 00 80 10 00 f0 bf 10 00 40 00 00
30: fc 40 00 00 00 44 00 00 fc 44 00 00 0a 01 00 05
40: cf 10 9a 10 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 0f 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: cf 10 9a 10 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 fe
e0: 00 c0 c0 24 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

localhost:~# lspci -s 00:0f.1 -xxx
0000:00:0f.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
00: 80 11 76 04 07 00 10 02 80 00 07 06 00 a8 82 00
10: 00 10 00 10 dc 00 00 02 00 06 09 b0 00 00 c0 10
20: 00 f0 ff 10 00 00 00 11 00 f0 3f 11 00 48 00 00
30: fc 48 00 00 00 4c 00 00 fc 4c 00 00 0a 02 80 05
40: cf 10 9a 10 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 0f 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: cf 10 9a 10 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 fe
e0: 00 40 c0 24 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Windows
-------

__ Device __     CardBus Bridge
                                                                              
                                                                              
  00 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F   Refresh    : ON        
  00 80 11 76 04 07 00 10 02 80 00 07 06 00 40 82 00                          
  10 00 00 00 00 DC 00 00 02 00 02 02 B0 00 00 10 0C   Rev ID        : 80     
  20 00 F0 1F 0C 00 00 00 00 00 00 00 00 FC FF 00 00   Int Line (IRQ): 0A     
  30 00 00 00 00 00 00 00 00 00 00 00 00 0A 01 00 04   Int Pin       : 01     
  40 CF 10 9A 10 01 00 00 00 00 00 00 00 00 00 00 00   Latency Timer : 40     
  50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Sub.Vendor ID : FFFC   
  60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Subsystem ID  : 0000   
  70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00                          
  80 00 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30   #0: 00000000 FFFFF000  
  90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #1: 020000DC 020000DC  
  A0 00 00 00 00 00 00 00 00 00 00 0F 00 00 00 00 00   #2: B0020200 F8FFFFFF  
  B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #3: 0C100000 FFFFF000  
  C0 CF 10 9A 10 00 00 00 00 00 00 00 00 00 00 00 00   #4: 0C1FF000 FFFFF000  
  D0 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 FE   #5: 00000000 FFFFF000  
  E0 00 C0 C0 24 00 00 00 00 00 00 00 00 00 00 00 00                          
  F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ROM: 00000000          
                                                                              
  Type: PCI        Bus: 00  Device: 0F  Function: 00                          
  Type value to modify.                                                       

  __ Device __     CardBus Bridge


  30 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F   Refresh    : ON
  00 80 11 76 04 07 00 10 02 80 00 07 06 00 40 82 00
  10 00 10 00 0C DC 00 00 02 00 03 03 B0 00 F0 FF FF   Rev ID        : 80
  20 00 00 00 00 00 F0 FF FF 00 00 00 00 FC FF FF FF   Int Line (IRQ): 0A
  30 00 00 00 00 FC FF 00 00 00 00 00 00 0A 02 80 04   Int Pin       : 02
  40 CF 10 9A 10 01 00 00 00 00 00 00 00 00 00 00 00   Latency Timer : 40
  50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Sub.Vendor ID : FFFC
  60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Subsystem ID  : FFFF
  70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  80 00 00 82 08 00 03 00 00 63 04 63 04 00 00 00 30   #0: 0C001000 FFFFF000
  90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #1: 020000DC 020000DC
  A0 00 00 00 00 00 00 00 00 00 00 0F 00 00 00 00 00   #2: B0030300 F8FFFFFF
  B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   #3: FFFFF000 FFFFF000
  C0 CF 10 9A 10 00 00 00 00 00 00 00 00 00 00 00 00   #4: 00000000 FFFFF000
  D0 00 00 00 00 00 00 00 00 00 00 00 00 01 00 19 FE   #5: FFFFF000 FFFFF000
  E0 00 40 C0 24 00 00 00 00 00 00 00 00 00 00 00 00
  F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ROM: 00000000

  Type: PCI        Bus: 00  Device: 0F  Function: 01

Perhaps the pcmcia-cs people can identify the registers that would affect 
card-initiated DMA transfer into the comm page..?

-Mercury



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo driver

[Giuliano Pochini]

On 23-Nov-2004 Yon Mercury wrote:

> OK, here's a comparison of the CardBus registers between Linux and Windows.
> As you can see, some registers are different-- take 0D for example.

I guess you got the register dump while the cards was in, didn't you ? 
Just to be sure :)  I'm asking this because the latency timer should
be 0xC0, not 0x40.


> The question is, what registers are likely to be the ones we have to change?

Register 0x80 should be 00 (PCI prefetch disabled).
Register 0x0D should be C0 (latency timer, the driver should be
able to set it, so don't touch it).

I don't know about all other registers because I couldn't find
any documentation. Registers >=0x80 are chip-specific and they
are explained here: http://pcmcia-cs.sourceforge.net/specs/AP476IIE10.pdf


--
Giuliano.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo driver

[Yon Mercury]

Giuliano,

Yes, the register dump was taken when the card was in. I tried manually
changing latency timer and pci prefetch but with no success. Running:

setpci -s 00:0f latency_timer=c0
setpci -s 00:0f 80.B=00

Shows changed values in lspci.
But still the driver fails to load when I do a 'modprobe snd-indigoio'. If I
try a '/etc/init.d/pcmcia restart' to restart CardBus services, all the PCI
settings return to their old values and I have to use setpci again.

This is getting to be a bit ridiculous. If this is a CardBus bridge issue,
someone with a different bridge chip should be able to get the Echo card
working, right? Does anyone out there on the list have audio working on a
CardBus system that could test an Echo card? 

Giuliano, have you heard from any of the other Echo Audio users who might have
one of those cards?

If it is a CardBus bridge issue, then we could take it up with the PCMCIA-CS
people. 

On the other hand, is it possible that its an Echo driver issue?

Cheers,
-Mercury


On Tue, 23 Nov 2004 10:41:38 +0100 (CET), Giuliano Pochini wrote
> On 23-Nov-2004 Yon Mercury wrote:
> 
> > OK, here's a comparison of the CardBus registers between Linux and Windows.
> > As you can see, some registers are different-- take 0D for example.
> 
> I guess you got the register dump while the cards was in, didn't you 
> ? Just to be sure :)  I'm asking this because the latency timer 
> should be 0xC0, not 0x40.
> 
> > The question is, what registers are likely to be the ones we have to change?
> 
> Register 0x80 should be 00 (PCI prefetch disabled).
> Register 0x0D should be C0 (latency timer, the driver should be
> able to set it, so don't touch it).
> 
> I don't know about all other registers because I couldn't find
> any documentation. Registers >=0x80 are chip-specific and they
> are explained here: http://pcmcia-cs.sourceforge.net/specs/AP476IIE10.pdf



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo driver

[Giuliano Pochini]

On 24-Nov-2004 Yon Mercury wrote:

> Yes, the register dump was taken when the card was in. I tried manually
> changing latency timer and pci prefetch but with no success. Running:
>
> setpci -s 00:0f latency_timer=c0
> setpci -s 00:0f 80.B=00
>
> Shows changed values in lspci.
> But still the driver fails to load when I do a 'modprobe snd-indigoio'. If I
> try a '/etc/init.d/pcmcia restart' to restart CardBus services, all the PCI
> settings return to their old values and I have to use setpci again.
>
> This is getting to be a bit ridiculous. If this is a CardBus bridge issue,
> someone with a different bridge chip should be able to get the Echo card
> working, right? Does anyone out there on the list have audio working on a
> CardBus system that could test an Echo card?

I talked with several people in the past who had Mona and Layla24
-cardbus version. None of them could make it work. The PCI version
of those cards works fine. Thus I guess the problem is not in the
driver, at least for the two cards above. But since the firmware
loading routine is the same for any card I don't think there is
an indigo-specific bug in this case. So, if it's unlikely it's
driver fault and other people has (partly unresolved) problems
with the PCMCIA interface, I guess the problems stays in the
interface also in this case.


> Giuliano, have you heard from any of the other Echo Audio users who
> might have one of those cards?

Yes, I'll contact them.


> On the other hand, is it possible that its an Echo driver issue?

Of course it's possible, but it's very unlikely.


--
Giuliano.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo CardBus driver

[Yon Mercury]

Giuliano,

I'm going to have to return the Indigo IO to the store soon. Not a peep from
the linux pcmcia people to my inquiry, and I feel stuck with it.

I'd love to have a working low cost, low latency laptop solution for linux
audio, but it hasn't quite materialized yet! But.. who knows, maybe someone
else will hit the magic button. I did my best.

-Mercury



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo CardBus driver

[Giuliano Pochini]

On 30-Nov-2004 Yon Mercury wrote:

> I'm going to have to return the Indigo IO to the store soon. Not a peep from
> the linux pcmcia people to my inquiry, and I feel stuck with it.
> 
> I'd love to have a working low cost, low latency laptop solution for linux
> audio, but it hasn't quite materialized yet! But.. who knows, maybe someone
> else will hit the magic button. I did my best.

I'm still investigating.  I don't know if and when I'll find
what's going wrong.  Sorry.


--
Giuliano.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo CardBus driver

[Yon Mercury]

On Tue, 30 Nov 2004 12:19:51 +0100 (CET), Giuliano Pochini wrote
> On 30-Nov-2004 Yon Mercury wrote:
> 
> > I'm going to have to return the Indigo IO to the store soon. Not a peep from
> > the linux pcmcia people to my inquiry, and I feel stuck with it.
> > 
> > I'd love to have a working low cost, low latency laptop solution for linux
> > audio, but it hasn't quite materialized yet! But.. who knows, maybe someone
> > else will hit the magic button. I did my best.
> 
> I'm still investigating.  I don't know if and when I'll find
> what's going wrong.  Sorry.

That's OK, you've done a lot already. I can always buy the Indigo back if it
becomes workable.

Best,
-Mercury





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Re: Echo CardBus driver

[Yon Mercury]

Good news, Giuliano--

Your 1.0.0 release of the Echo audio driver works with the Indigo IO CardBus
on my laptop. I went to the store to give it another crack, and she runs.
Capture, playback and monitor are all working at 64 sample latency. Nice work!

Thanks for your persistence.
-Mercury



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

RE: Re: Echo driver

[Yon Mercury]

Giuliano,

On Wed, 10 Nov 2004 09:27:10 +0100 (CET), Giuliano Pochini wrote
> I don't know, but nobody who tried an echoaudio card had success.

Really? Not even you?

> Look at this for example:
> http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg12364.html
> 
> but other people did try the same trick with no good results,
> so it's at least bridge-specific or, worse, computer-specific.

If you follow that thread, you get to another, where a second person solves
his cardbus problem:
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg12641.html

>From the thread, it does seem that different cardbus bridges require special
tweaks-- but those people seem to be suggesting that it is an issue with the
Linux PCMCIA implementation and not ALSA. One of their fixes has already been
implemented into the PCMCIA tree.

What you could do is put out a call for anyone with a CardBus Echo card to
test your driver. What do you think?

-Mercury




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

RE: Re: Echo driver

[Giuliano Pochini]

On 11-Nov-2004 Yon Mercury wrote:
> Giuliano,
>
> On Wed, 10 Nov 2004 09:27:10 +0100 (CET), Giuliano Pochini wrote
>> I don't know, but nobody who tried an echoaudio card had success.
>
> Really? Not even you?

I don't have a laptop.


> From the thread, it does seem that different cardbus bridges require special
> tweaks-- but those people seem to be suggesting that it is an issue with the
> Linux PCMCIA implementation and not ALSA. One of their fixes has already been
> implemented into the PCMCIA tree.
>
> What you could do is put out a call for anyone with a CardBus Echo card to
> test your driver. What do you think?

Usually people call me when they have problems. The new driver
have a new firmware and it may make some difference. I'll contact
those people to ask them to try the new driver. I have to finish
it, though, I need some more time. Currently I ported only Darla20,
Gina20, Darla24, Gina24 and Layla20 (no midi yet because I must
rewrite it and I prefer to do that work last).


--
Giuliano.


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

RE: Re: Echo driver

[Yon Mercury]

Giuliano,

On Thu, 11 Nov 2004 09:31:48 +0100 (CET), Giuliano Pochini wrote
> > What you could do is put out a call for anyone with a CardBus Echo card to
> > test your driver. What do you think?
> 
> Usually people call me when they have problems. The new driver
> have a new firmware and it may make some difference. I'll contact
> those people to ask them to try the new driver. I have to finish
> it, though, I need some more time. Currently I ported only Darla20,
> Gina20, Darla24, Gina24 and Layla20 (no midi yet because I must
> rewrite it and I prefer to do that work last).

An update- I have put an Indigo IO CardBus on order, and I'd like to help
getting the Echo driver to support it. If that means fiddling with the CardBus
bridge support, so be it.  

Giuliano, will you be ready for a tester in a couple weeks?

Regards,
-Mercury



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

Re: Echo driver

[Yon Mercury]

> Giuliano Pochini <pochini@shiny.it> wrote:
> Perhaps I'll put the driver in bugfixes-only state because it's very 
> stable and ready for production for a long time now and because 
> Echoaudio has just released a new version of their generic code that 
> support all cards and I want to start working of it ASAP. There are 
> several changes to the DSP firmware that may cause incompatibilities 
> with the current driver (maybe not, I only had a look at the notes).

So Echo released the new driver they have been promising? It's odd that that
would happen right after we emailed them. Maybe it goes to show what a little
grassroots action can do. Or maybe it's just a coinkidink. 

Let us know how your work proceeds on the driver, Giuliano, and thanks.

-Mercury



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

RE: Re: Echo driver

[Giuliano Pochini]

On 07-Nov-2004 Yon Mercury wrote:
>> Giuliano Pochini <pochini@shiny.it> wrote:
>> Perhaps I'll put the driver in bugfixes-only state because it's very
>> stable and ready for production for a long time now and because
>> Echoaudio has just released a new version of their generic code that
>> support all cards and I want to start working of it ASAP. There are
>> several changes to the DSP firmware that may cause incompatibilities
>> with the current driver (maybe not, I only had a look at the notes).
>
> So Echo released the new driver they have been promising?

Yes: http://www.echoaudio.com/Downloads/license_agreement.php
and I already started to work on it. The new firmware
has some differences on almost all cards, so I have to
change the code for old cards too.


--
Giuliano.


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click