lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071026163651.GD4321@flint.arm.linux.org.uk> Date: Fri, 26 Oct 2007 17:36:51 +0100 From: Russell King <rmk+lkml@....linux.org.uk> To: Rodolfo Giometti <giometti@...eenne.com> Cc: linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] PCMCIA: prevent auto insert during resume. On Fri, Oct 26, 2007 at 06:27:06PM +0200, Rodolfo Giometti wrote: > On Fri, Oct 26, 2007 at 05:02:06PM +0100, Russell King wrote: > > When you bring the battery device out of resume, and you've inserted a > > card, you want it to be detected. Your change means you have to wait > > until the system has finished resuming before you plug the card in, > > which practically is a pain in the butt and actually leads to user > > errors. IOW: > > > > "I plugged my wireless card in after I pressed the power button, why > > wasn't it detected?" > > My patch doesn't affect the power on sequence, just the resume > one. On a lot of devices, the "power button" is the resume button. When you "turn it off" it suspends, and when you "turn it on" it resumes. > 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. I realise that. I do work on embedded devices, and this behaviour is explicitly there to support embedded devices. I've suggested a workable solution to you which allows both of us to have the behaviour we both desire from the system. That sounds like a negotiated solution to me... -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists