From: Pavel Machek <pavel@suse.cz>
To: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
p_gortmaker@yahoo.com
Subject: Re: swsuspend not working
Date: Fri, 6 Aug 2004 21:06:49 +0200 [thread overview]
Message-ID: <20040806190649.GC3048@elf.ucw.cz> (raw)
In-Reply-To: <20040731182001.GA6760@lps.ens.fr>
Hi!
> > > ? Destination Host Unreachable ? and nothing more. The interrupt count of
> > > the card is increasing, however. Unloading and reloading ne2k_pci fixes
> > > that.
> >
> > Teach ne2k_pci to do on suspend what it does on unload, and to do on
> > resume what it does on load. Should be easy.
>
> ? Should be easy ? is easily said. Well.
:-)))).
> The following patch to drivers/net/ne2k-pci.c in 2.6.8-rc1 happens to make
> my pci ethernet card (Realtek Semiconductor Co., Ltd. RTL-8029(AS))
> suspend to S4 and resume properly.
>
> I know nothing on suspend/resume architecture, I know nothing on
> programming ethernet card, I know nothing on patching device drivers; I
> just looked at other drivers, picked function calls that had nice looking
> names and put them together in ne2k_pci.c. Miraculously, it works.
>
> Do you think it could get in ?
Yes, the patch looks good to me, submit it through ne2k-pci
maintainer...
Pavel
> --- ne2k-pci.c.orig 2004-07-20 22:15:30.000000000 +0200
> +++ ne2k-pci.c 2004-07-31 19:48:38.000000000 +0200
> @@ -653,12 +653,43 @@
> pci_set_drvdata(pdev, NULL);
> }
>
> +#ifdef CONFIG_PM
> +static int ne2k_pci_suspend (struct pci_dev *pdev, u32 state)
> +{
> + struct net_device *dev = pci_get_drvdata (pdev);
> +
> + netif_device_detach(dev);
> + ne2k_pci_close(dev);
> + ne2k_pci_reset_8390(dev);
> + pci_set_power_state (pdev, state);
> +
> + return 0;
> +}
> +static int ne2k_pci_resume (struct pci_dev *pdev)
> +{
> + struct net_device *dev = pci_get_drvdata (pdev);
> +
> + pci_set_power_state(pdev, 0);
> + ne2k_pci_reset_8390(dev);
> + ne2k_pci_open(dev);
> + netif_device_attach(dev);
> +
> + return 0;
> +}
> +
> +#endif /* CONFIG_PM */
> +
>
> static struct pci_driver ne2k_driver = {
> .name = DRV_NAME,
> .probe = ne2k_pci_init_one,
> .remove = __devexit_p(ne2k_pci_remove_one),
> .id_table = ne2k_pci_tbl,
> +#ifdef CONFIG_PM
> + .suspend = ne2k_pci_suspend,
> + .resume = ne2k_pci_resume,
> +#endif /* CONFIG_PM */
> +
> };
>
>
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-08-06 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040715121042.GB9873@lps.ens.fr.suse.lists.linux.kernel>
2004-07-15 12:10 ` swsuspend not working Éric Brunet
2004-07-15 12:18 ` Pavel Machek
2004-07-15 13:23 ` Éric Brunet
2004-07-15 13:21 ` Nigel Cunningham
2004-07-19 19:19 ` Éric Brunet
2004-07-20 13:17 ` Pavel Machek
2004-07-20 15:50 ` Romano Giannetti
2004-07-31 18:20 ` Éric Brunet
2004-08-06 19:06 ` Pavel Machek [this message]
2004-08-06 23:54 ` Éric Brunet
2004-08-07 7:13 ` Paul Gortmaker
[not found] ` <20040807140845.GA8353@lps.ens.fr>
2004-08-21 12:14 ` PATCH swsuspend for ne2k-pci cards Éric Brunet
2004-08-23 19:51 ` Pavel Machek
2004-09-01 14:56 ` PATCH (RESENT) " Éric Brunet
2004-07-15 12:47 ` swsuspend not working Stefan Seyfried
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=20040806190649.GC3048@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=Eric.Brunet@lps.ens.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
/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