From: Russell King <rmk+pcmcia@arm.linux.org.uk>
To: Dave <kilroyd@googlemail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pcmcia@lists.infradead.org,
orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org,
Dominik Brodowski <linux@dominikbrodowski.net>,
Andrey Borzenkov <arvidjaar@mail.ru>
Subject: Re: [Orinoco-devel] 2.6.28-rc2: new PCMCIA device instance after resume - orinoco can't download firmware
Date: Wed, 29 Oct 2008 21:51:42 +0000 [thread overview]
Message-ID: <20081029215142.GA29780@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4908CD44.8070503@gmail.com>
On Wed, Oct 29, 2008 at 08:53:24PM +0000, Dave wrote:
> Looking at the pcmcia code it looks like ds_event is getting a
> CS_EVENT_CARD_INSERTION event. Should we be processing that event ?
You can get that on resume if PCMCIA thinks the card has changed -
and it determines that by comparing its cache of the CIS with what
is in the card on resume. If the cache doesn't match the CIS, it
assumes the card has changed, and does a remove-insert cycle instead
of resume.
So the question to ask is: why is the card's CIS changing on resume?
Try putting some debug in verify_cis_cache() in drivers/pcmcia/cistpl.c.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-10-29 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 19:19 2.6.28-rc2: new PCMCIA device instance after resume - orinoco can't download firmware Andrey Borzenkov
2008-10-29 0:42 ` Dominik Brodowski
2008-10-29 3:43 ` Andrey Borzenkov
2008-10-29 12:18 ` Rafael J. Wysocki
2008-10-29 15:19 ` Andrey Borzenkov
2008-10-29 18:49 ` [Orinoco-devel] " Dave
2008-10-29 20:43 ` Rafael J. Wysocki
2008-10-29 20:53 ` Dave
2008-10-29 21:34 ` Rafael J. Wysocki
2008-10-29 21:51 ` Russell King [this message]
2008-10-30 18:15 ` Dave
2008-10-30 18:39 ` Andrey Borzenkov
2008-10-30 22:46 ` Rafael J. Wysocki
2008-10-29 0:49 ` Dave
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=20081029215142.GA29780@flint.arm.linux.org.uk \
--to=rmk+pcmcia@arm.linux.org.uk \
--cc=arvidjaar@mail.ru \
--cc=kilroyd@googlemail.com \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).