[lkml]   [2003]   [May]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: request_firmware() hotplug interface, third round.
On Sat, May 17, 2003 at 12:13:49AM +0200, Oliver Neukum wrote:
> Am Freitag, 16. Mai 2003 18:09 schrieb Alan Cox:
> > On Gwe, 2003-05-16 at 09:07, Oliver Neukum wrote:
> > > So, if I understand you correctly, RAM is only saved if a device
> > > is hotpluggable and needs firmware only upon intial connection.
> > > Which, if you do suspend to disk correctly, is no device.
> >
> > Thats just because the interface is a little warped not the theory.
> > On a resume you need to reload firmware and you already handle
> > rediscovery on USB bus for example because the devices can change
> Right. But the order of resumption is fixed by hardware needs.
> So during resumption you cannot use block devices and therefore
> not start a hotplug script. Or did I miss something?

For devices that aren't essentialy to get userspace running
(e.g. network on a laptop running from local disk), the firmware
request doesn't have to happen during the hairy part of resumption.

The device could just mark itself as unusable at suspend time, then at
resume it schedule_work()s something to reload the firmware and
complete reinitialization. Shortly after userspace is back in action,
the device will come back to life.

David Gibson | For every complex problem there is a | solution which is simple, neat and
| wrong.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:35    [W:0.104 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site