Re: [PATCH] Remove process freezer from suspend to RAM pathway

Am Sonntag, 8. Juli 2007 schrieb Benjamin Herrenschmidt:
> Another issue that's been a problem forever with suspend is the
> synchronous request_firmware interface. Lots of drivers do that in
> resume() which will generally not work.

Unfortunately yes they do. We now have the notifier chains, which
can be used. Firmware, especially if it is large, must be requested
while the system is still fully functional and paging will work.

Asynchronocity will not help much because the devices must work
after resumingand delaying that will not help with respect to needing
devices to get at the firmware.

	Regards
		Oliver

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: Benjamin Herrenschmidt <[email protected]>

• References:
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: Alan Stern <[email protected]>
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: Benjamin Herrenschmidt <[email protected]>

• Prev by Date: Re: 2.6.22 -- net/core/dev.c:1515: error: 'NETIF_F_IPV6_CSUM' undeclared (first use in this function)
• Next by Date: Re: Documentation of kernel messages (Summary)
• Previous by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
• Next by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]