| 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: <4A054884.3060503@s5r6.in-berlin.de> Date: Sat, 09 May 2009 11:10:28 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Kenneth Crudup <kenny@...ix.com> CC: linux-pm@...ts.linux-foundation.org, tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce Kenneth Crudup wrote: > Oh, and I can hit "ESC" in the middle of suspending with TuxOnIce and > back out of it if I'd changed my mind for whatever reason. > > There are(/were) competing ieee1394 OHCI drivers and competing Bluetooth > USB HCI drivers, and that's just off the top of my head- so having > competing suspend/resume methods won't be anything new. Let the market > decide which is best. The case of two 1394 driver stacks isn't fully comparable. I supported the addition of the second stack with the intent to replace the existing one after a transition period, and in the hope that the ratio of available maintainer manpower : size and complexity of the codebase would improve considerably. Because that was/is the single fundamental problem in Linux 1394 driver land. (Besides, how well is infrastructure like the suspend--resume framework comparable to drivers?) -- Stefan Richter -=====-=-=== -=-= -==-= http://arcgraph.de/sr/ -- 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