From: Russell King <rmk@arm.linux.org.uk>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>, John Belmonte <jvb@prairienet.org>
Subject: Re: 2.5.75-mm1 yenta-socket lsPCI IRQ reads incorrect
Date: Tue, 15 Jul 2003 08:56:22 +0100 [thread overview]
Message-ID: <20030715085622.A32119@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200307151331.40428.mflt1@micrologica.com.hk>; from mflt1@micrologica.com.hk on Tue, Jul 15, 2003 at 01:31:37PM +0800
On Tue, Jul 15, 2003 at 01:31:37PM +0800, Michael Frank wrote:
> problems seen:
>
> - yenta_probe pci_save_state saves irq as ff. Moved to end of function, result same
irq was 0xff at boot, so it is neither here nor there whether it remains
0xff after a resume. If it works at boot with 0xff, it should work after
a resume with 0xff.
> - both swsusp and ACPI/S3 do _not_ call yenta_suspend and yenta_init,
> so it still wont work
Please confirm whether pcmcia_socket_dev_suspend() is called from
yenta.c with SUSPEND_SAVE_STATE and not zero. (it should be
SUSPEND_SAVE_STATE.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-07-15 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 5:41 Yenta_socket lsPCI IRQ reads incorrect Michael Frank
2003-07-14 9:07 ` Pavel Machek
2003-07-14 9:28 ` 2.5.75-mm1 yenta-socket " Michael Frank
2003-07-14 11:01 ` Russell King
2003-07-14 11:37 ` Michael Frank
2003-07-14 14:50 ` Russell King
2003-07-14 15:04 ` Jeff Garzik
2003-07-14 15:21 ` Russell King
2003-07-14 15:18 ` Michael Frank
2003-07-14 15:34 ` Russell King
2003-07-14 15:27 ` Michael Frank
2003-07-15 5:31 ` Michael Frank
2003-07-15 6:08 ` Michael Frank
2003-07-15 7:56 ` Russell King [this message]
2003-07-15 9:34 ` Michael Frank
2003-07-15 10:42 ` Michael Frank
2003-07-15 14:39 ` Russell King
2003-07-15 16:09 ` Michael Frank
2003-07-16 3:16 ` Michael Frank
2003-07-16 5:04 ` Michael Frank
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=20030715085622.A32119@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jvb@prairienet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
--cc=pavel@suse.cz \
/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.