public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "christophe barbé" <christophe.barbe.ml@online.fr>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@zip.com.au>
Subject: Re: [PATCH] 3c59x and resume
Date: Mon, 25 Mar 2002 19:57:19 -0500	[thread overview]
Message-ID: <3C9FC76F.6050900@mandrakesoft.com> (raw)
In-Reply-To: <20020323161647.GA11471@ufies.org>

christophe barbé wrote:

>Here is a small patch tested with 2.4.18 and 2.4.19-pre4.
>It was proposed by Andrew but not integrated in pre4.
>
>The problem is when using the vortex driver and suspend/resuming the
>machine. Without this patch the card id is each time greater. To resume
>correctly this driver need the option enable_wol=1 but as-is it will
>only be true for the first ID. You can enable it for the first 8 IDs
>with enable_wol=1,1,1,1,1,1,1,1 but you can't do it for all IDs.
>Said another way without this patch you can't suspend/resume more than
>eight times your machine.
>
>This is a fix for the most common use. The proper fix would be IMO to
>keep a bitmap of used IDs but I don't know if it worsts it.
>Also a fix would be to separate the suspend/resume functionality from
>the wol functionality (wake up on lan).
>
>Thanks,
>Christophe
>
>--- linux/drivers/net/3c59x.c	Sat Mar 23 10:24:56 2002
>+++ linux/drivers/net/3c59x.c	Sat Mar 23 10:57:00 2002
>@@ -2891,6 +2891,9 @@
> 
> 	vp = dev->priv;
> 
>+	if (vp->card_idx == vortex_cards_found - 1)
>+         vortex_cards_found--;
>+
> 	/* AKPM: FIXME: we should have
> 	 *	if (vp->cb_fn_base) iounmap(vp->cb_fn_base);
> 	 * here
>

This patch causes module defaults to be reused -- potentially incorrectly.

This is a personal solution, that might live on temporary as an 
outside-the-tree patch... but we cannot apply this to the stable kernel.

I agree the card idx is wrong on remove.  Insert and remove a 3c59x 
cardbus card several times, and you will lose your module options too. 
 However... take note that this problem cannot be solved "the easy way" 
-- because one solution people may desire will potentially result in 
module options getting re-used incorrectly.  The above is one such solution.

If you want WOL options to "stick" or vary per-interface, we already 
have an API for that -- ethtool.  Check out drivers/net/natsemi.c for an 
example implementation.  _Tested_ patches to 3c59x that add WOL ethtool 
support are welcome, pending Andrew's approval.  Do not remove 
enable_wol for now in a stable series, but we will deprecate its use 
once ethtool support appears.

    Jeff






  parent reply	other threads:[~2002-03-26  0:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-23 16:16 [PATCH] 3c59x and resume christophe barbé
2002-03-23 18:39 ` Andrew Morton
2002-03-23 20:06   ` Robert Love
2002-03-23 22:44     ` christophe barbé
2002-03-24  8:07       ` Greg KH
2002-03-24 14:25         ` christophe barbé
2002-03-25 18:01           ` Greg KH
2002-03-25 18:19             ` christophe barbé
2002-03-25 19:11               ` Greg KH
2002-03-25 20:27                 ` christophe barbé
2002-03-25 20:58                 ` christophe barbé
2002-03-25 11:34     ` Joachim Breuer
2002-03-25 11:53       ` Xavier Bestel
2002-03-25 21:31         ` Joachim Breuer
2002-03-25 19:44     ` Bill Davidsen
2002-03-25 20:16       ` christophe barbé
2002-03-26  0:57 ` Jeff Garzik [this message]
2002-03-26  1:40   ` christophe barbé
2002-03-26  4:10     ` Jeff Garzik
2002-03-26  4:39       ` christophe barbé
2002-03-26  4:50         ` Andrew Morton
2002-03-26 16:56           ` christophe barbé
2002-03-26 16:57             ` Jeff Garzik

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=3C9FC76F.6050900@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=akpm@zip.com.au \
    --cc=christophe.barbe.ml@online.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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