* Re: Re: Echo driver [not found] ` <XFMail.20041122172923.pochini@shiny.it> @ 2004-11-23 0:02 ` Yon Mercury 2004-11-23 0:45 ` Yon Mercury 1 sibling, 0 replies; 9+ messages in thread From: Yon Mercury @ 2004-11-23 0:02 UTC (permalink / raw) To: Giuliano Pochini; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo driver [not found] ` <XFMail.20041122172923.pochini@shiny.it> 2004-11-23 0:02 ` Re: Echo driver Yon Mercury @ 2004-11-23 0:45 ` Yon Mercury 2004-11-23 9:41 ` Giuliano Pochini 1 sibling, 1 reply; 9+ messages in thread From: Yon Mercury @ 2004-11-23 0:45 UTC (permalink / raw) To: Giuliano Pochini; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo driver 2004-11-23 0:45 ` Yon Mercury @ 2004-11-23 9:41 ` Giuliano Pochini 2004-11-24 3:14 ` Yon Mercury 0 siblings, 1 reply; 9+ messages in thread From: Giuliano Pochini @ 2004-11-23 9:41 UTC (permalink / raw) To: Yon Mercury; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo driver 2004-11-23 9:41 ` Giuliano Pochini @ 2004-11-24 3:14 ` Yon Mercury 2004-11-24 8:40 ` Giuliano Pochini 0 siblings, 1 reply; 9+ messages in thread From: Yon Mercury @ 2004-11-24 3:14 UTC (permalink / raw) To: Giuliano Pochini; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo driver 2004-11-24 3:14 ` Yon Mercury @ 2004-11-24 8:40 ` Giuliano Pochini 2004-11-30 5:53 ` Re: Echo CardBus driver Yon Mercury 0 siblings, 1 reply; 9+ messages in thread From: Giuliano Pochini @ 2004-11-24 8:40 UTC (permalink / raw) To: Yon Mercury; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo CardBus driver 2004-11-24 8:40 ` Giuliano Pochini @ 2004-11-30 5:53 ` Yon Mercury 2004-11-30 11:19 ` Giuliano Pochini [not found] ` <20041207214612.1951d3bb.pochini@shiny.it> 0 siblings, 2 replies; 9+ messages in thread From: Yon Mercury @ 2004-11-30 5:53 UTC (permalink / raw) To: Giuliano Pochini; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo CardBus driver 2004-11-30 5:53 ` Re: Echo CardBus driver Yon Mercury @ 2004-11-30 11:19 ` Giuliano Pochini 2004-11-30 19:25 ` Yon Mercury [not found] ` <20041207214612.1951d3bb.pochini@shiny.it> 1 sibling, 1 reply; 9+ messages in thread From: Giuliano Pochini @ 2004-11-30 11:19 UTC (permalink / raw) To: Yon Mercury; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Echo CardBus driver 2004-11-30 11:19 ` Giuliano Pochini @ 2004-11-30 19:25 ` Yon Mercury 0 siblings, 0 replies; 9+ messages in thread From: Yon Mercury @ 2004-11-30 19:25 UTC (permalink / raw) To: Giuliano Pochini, Yon Mercury; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <20041207214612.1951d3bb.pochini@shiny.it>]
[parent not found: <20041214181755.M17861@stickist.com>]
[parent not found: <Pine.LNX.4.58.0412142205520.10830@denise.shiny.it>]
* Re: Re: Echo CardBus driver [not found] ` <Pine.LNX.4.58.0412142205520.10830@denise.shiny.it> @ 2004-12-23 2:44 ` Yon Mercury 0 siblings, 0 replies; 9+ messages in thread From: Yon Mercury @ 2004-12-23 2:44 UTC (permalink / raw) To: Giuliano Pochini; +Cc: alsa-devel 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/ ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2004-12-23 2:44 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20041122021637.M69154@stickist.com>
[not found] ` <XFMail.20041122172923.pochini@shiny.it>
2004-11-23 0:02 ` Re: Echo driver Yon Mercury
2004-11-23 0:45 ` Yon Mercury
2004-11-23 9:41 ` Giuliano Pochini
2004-11-24 3:14 ` Yon Mercury
2004-11-24 8:40 ` Giuliano Pochini
2004-11-30 5:53 ` Re: Echo CardBus driver Yon Mercury
2004-11-30 11:19 ` Giuliano Pochini
2004-11-30 19:25 ` Yon Mercury
[not found] ` <20041207214612.1951d3bb.pochini@shiny.it>
[not found] ` <20041214181755.M17861@stickist.com>
[not found] ` <Pine.LNX.4.58.0412142205520.10830@denise.shiny.it>
2004-12-23 2:44 ` Yon Mercury
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.