On Fri, Oct 26, 2007 at 05:02:06PM +0100, Russell King wrote:This can be done by a button, menu or other graphical object. :) Yes. This have some reasons... for example, my custom board has a WiFi connected to the PCMCIA interface (which consumes a lot of power) and if the user switch off the WiFi I think he/she doesn't wish the WiFi is automagic powered on after resume... this behaviour can cause power lost if the user forgot to switch it off again. My patch doesn't affect the power on sequence, just the resume one. Also if you didn't eject the socket, at resume the device will be powered up again, my patch just prevents that a pre-powered off device to be turned on at resume time. However you should consider that some embedded systems have fixed PCMCIA devices that can't be removed so there are no reasons to detect them after resume, nobody can change them. :) Also battery powered devices can go very frequently to sleep and the current behavior force the user to switch off the unused device each time the system resumes from sleep. Ciao, Rodolfo -- GNU/Linux Solutions e-mail: giometti@enneenne.com Linux Device Driver giometti@gnudd.com Embedded Systems giometti@linux.it UNIX programming phone: +39 349 2432127 -
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Linus Torvalds | Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series.. |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [klibc] [patch] import socket defines |
