From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
linux-wireless@vger.kernel.org, linux-pcmcia@lists.infradead.org,
orinoco-devel@lists.sourceforge.net
Subject: Re: 2.6.28-rc2: new PCMCIA device instance after resume - orinoco can't download firmware
Date: Wed, 29 Oct 2008 18:19:16 +0300 [thread overview]
Message-ID: <200810291819.20848.arvidjaar@mail.ru> (raw)
In-Reply-To: <200810291318.05373.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Wednesday 29 October 2008, Rafael J. Wysocki wrote:
>
> > Do you have any idea what could it be? Original message is here:
> > http://marc.info/?l=linux-wireless&m=122522165719760&w=2
>
> This probably is a result of the fact that we don't include firmware blobs
> into modular drivers any more. Please try to compile your driver directly
> into the kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>
> If this helps, we'll know what the problem is.
>
Ehh ... you miss the point. The problem is NOT missing firmware (I have
already been running with external firmware just fine in 2.6.27). The
problem is that during resume instead of simply resume *existing*
device/driver instance PCMCIA suddenly decides to re-discover the *same*
device yet another again.
This is not supposed to happen. I do not see any changes in
drivers/pcmcia that could be responsible for it - so I suspect there could
be some overall power management changes.
And personally I'd rather turned on debugging options; bisecting will
take ages here. I need some advice which options to turn on.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-29 15:19 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 [this message]
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
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=200810291819.20848.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).