From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Silla Rizzoli <silla@netvalley.it>
Cc: linux-kernel@vger.kernel.org,
Russell King <rmk+lkml@arm.linux.org.uk>,
David Hinds <dahinds@users.sourceforge.net>
Subject: Re: 2.4.25 yenta problem and small fix/workaround
Date: Thu, 19 Feb 2004 10:14:33 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0402191011470.29796@logos.cnet> (raw)
In-Reply-To: <200402191222.45709.silla@netvalley.it>
On Thu, 19 Feb 2004, Silla Rizzoli wrote:
> Hello!
> Inserting a PC Card in my laptop (IMB R40 2681) with kernel 2.4.25 results in
> the following message:
>
> Feb 19 11:10:16 [kernel] cs: socket d603e000 voltage interrogation timed out
>
> This sometimes happens with 2.6.x too, but issuing cardctl insert 0 usually
> solves the problem, however in this case it didn't. I tried to modify all the
> pcmcia_core module parameters but to no avail, the socket remained dead.
>
> Examining the sources I noticed that 2.4.25 introduced this three line check;
> I suppose that the socket state read returns a valid state and
> cb_writel(socket, CB_SOCKET_FORCE, CB_CVSTEST) is not executed.
> Removing the check and executing the last line regardless fixes the problem.
> I am probably experiencing a hardware bug limited to my laptop, but I'm
> posting this small patch here just in case someone has the same problem.
>
> Regards,
> Silla Rizzoli
>
>
>
> --- ./drivers/pcmcia/yenta.c.orig 2004-02-19 11:44:29.000000000 +0100
> +++ ./drivers/pcmcia/yenta.c 2004-02-19 11:43:45.000000000 +0100
> @@ -676,9 +676,6 @@
> exca_writeb(socket, I365_GENCTL, 0x00);
>
> /* Redo card voltage interrogation */
> - state = cb_readl(socket, CB_SOCKET_STATE);
> - if (!(state & (CB_CDETECT1 | CB_CDETECT2 | CB_5VCARD |
> - CB_3VCARD | CB_XVCARD | CB_YVCARD)))
>
> cb_writel(socket, CB_SOCKET_FORCE, CB_CVSTEST);
> }
Hi Silla,
Unfortunately this change fixes other problems (in Acer TravelMate laptops
for one I know, maybe others).
Someone needs to figure out a way for detection to work properly on both
setups.
next prev parent reply other threads:[~2004-02-19 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 11:22 Silla Rizzoli
2004-02-19 13:14 ` Marcelo Tosatti [this message]
2004-02-19 12:58 ` Silla Rizzoli
2004-02-19 20:32 ` David Hinds
2004-02-20 10:36 ` Silla Rizzoli
2004-02-20 22:31 Daniel Ritz
2004-02-21 12:28 ` Silla Rizzoli
2004-02-21 17:12 ` Daniel Ritz
2004-02-22 16:03 ` Silla Rizzoli
2004-02-22 16:30 ` Russell King
2004-02-22 17:20 ` Silla Rizzoli
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=Pine.LNX.4.58L.0402191011470.29796@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=dahinds@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=silla@netvalley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®