From: "Yon Mercury" <swirlee@stickist.com>
To: Giuliano Pochini <pochini@shiny.it>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: Echo driver
Date: Tue, 23 Nov 2004 20:14:06 -0700 [thread overview]
Message-ID: <20041124031406.M70915@stickist.com> (raw)
In-Reply-To: <XFMail.20041123104138.pochini@shiny.it>
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/
next prev parent reply other threads:[~2004-11-24 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[not found] <20041109203858.M64061@stickist.com>
[not found] ` <XFMail.20041110092710.pochini@shiny.it>
2004-11-11 3:45 ` Re: Echo driver Yon Mercury
2004-11-11 8:31 ` Giuliano Pochini
2004-11-13 23:41 ` Yon Mercury
2004-11-07 18:52 Yon Mercury
2004-11-08 8:29 ` Giuliano Pochini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041124031406.M70915@stickist.com \
--to=swirlee@stickist.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pochini@shiny.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.