From: Alexander Gran <alex@zodiac.dnsalias.org>
To: Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] Enable suspend/resuming of e1000
Date: Tue, 1 Jun 2004 15:54:48 +0200
User-Agent: KMail/1.6.2
References: <200405281404.10538@zodiac.zodiac.dnsalias.org> <200406011541.26425@zodiac.zodiac.dnsalias.org> <20040601135017.GB10040@elf.ucw.cz>
In-Reply-To: <20040601135017.GB10040@elf.ucw.cz>
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200406011554.48333@zodiac.zodiac.dnsalias.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 910
Lines: 25

Am Dienstag, 1. Juni 2004 15:50 schrieben Sie:
> What happens if you unload/reload module around suspend?

doesn't work. This was my first attempt. Seems that the pci_save_state, 
pci_disable device is really needed.

> You may want to free_irq in suspend routine and request it back in
> resume.

I also thought about that, however I tried to let e1000_suspend call 
e1000_down everytime, as that calls e1000_irq_disable and free_irq. Than call 
e1000_up in resume, as that does  request_irq e1000_irq_enable. 
This does not work, though. Still no irqs

Alex


-- 
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/