mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ciprian Docan <docan@eden.rutgers.edu>,
	netdev@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	"Rafael, J. Wysocki" <rjw@sisk.pl>
Subject: Re: Suspend/resume - slow resume
Date: Mon, 18 Apr 2011 20:08:13 +0200	[thread overview]
Message-ID: <20110418180813.GA18469@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <BANLkTi=tPc6NmUuTYqbVZduNRNbE=-c34Q@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> :
[lots of silly bugs]

Ok. it should be fixed for wednesday.

[...]
>  - unload not on close, but on device unregister (iow not when you do
> "ifconfig eth0 down", but when the "eth0" device really goes away)

Without further action, the firmware(s) will thus be locked in until the
driver is removed. 

> But as mentioned, the above is (a) just my gut feel - please discuss -
> and (b) I really think that leaving this to the network driver has
> been shown to continually result in the drivers doing the firmware
> load/unload in all the wrong places.

As long as it can be fixed... If the 60s delay is removed and the firmware
loading emits some messages for programmer barbie, I am more than happy.

If someone can tell me where Realtek's firmware should be sent to as David
W. seems to be busy, it will be perfect.

-- 
"Lack of vision" Ueimor

  reply	other threads:[~2011-04-18 18:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SOC.4.64.1104150931390.1320@er3.rutgers.edu>
     [not found] ` <BANLkTinO+HFq+Mgg1aUz9V==zYs7qSBtDw@mail.gmail.com>
     [not found]   ` <Pine.SOC.4.64.1104151122330.1320@er3.rutgers.edu>
2011-04-15 16:14     ` Linus Torvalds
2011-04-17 10:17       ` Francois Romieu
2011-04-17 16:42         ` Linus Torvalds
2011-04-18 18:08           ` Francois Romieu [this message]
2011-04-18 18:49             ` Linus Torvalds
2011-04-18 19:25               ` Ben Hutchings
2011-04-18 19:27               ` Ciprian Docan
2011-04-18 19:51                 ` Linus Torvalds
2011-04-20 18:16                   ` Francois Romieu
2011-04-20 18:51                     ` Ciprian Docan
2011-04-20 19:52                       ` Francois Romieu
2011-04-20 19:10                     ` Ciprian Docan
2011-04-20 19:53                       ` Francois Romieu
2011-04-21  2:07                         ` Ciprian Docan
2011-04-21 13:02                           ` Francois Romieu

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=20110418180813.GA18469@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=docan@eden.rutgers.edu \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®