Re: suspend/resume support for driver requires an external firmware

[Dmitry Torokhov <dtor_core@ameritech.net>]

On Monday 27 September 2004 05:47 pm, Denis Vlasenko wrote:
> On Monday 27 September 2004 21:19, Dmitry Torokhov wrote:
> > On Monday 27 September 2004 12:19 pm, Oliver Neukum wrote:
> > > > Why not just suspend the device first, then enter the system suspend
> > > > state; then on resume, resume the device after control has transferred
> > > > back to userspace. That way, the driver can load the firmware from the
> > > 
> > > And thus cause errors in all applications wishing to use the network
> > > until the firmware is reloaded. It is precisely what cannot be done.
> > > The firmware must be present on suspend. The question is, how?
> > 
> > While non-availability might be an issue for other types of hardware I think
> > it is ok for network cards. In many cases the interface will have to be
> > reconfigured at resume anyway (you move from office to home and the network
> > is completely different). Can't resume be handled by virtually removing/
> > inserting the device so firmware will be re-loaded as it was just a normal
> > startup?
> 
> Think about situation when all filesystems are NFS-mounted.
> You absolutely are not allowed to lose your network, or else hotplug
> (and all fs-backed stuff in general) will die horribly.

Where do you load your firmware from so that you can bring up the network
so you can mount everything via NFS in the first place?

-- 
Dmitry