Date: Sun, 27 Jul 2008 18:40:39 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Laptop suggestions? Message-ID: <5f67a8c40807271540m3e1354d8s4e8d10e7f101afac@mail.gmail.com> In-Reply-To: <20080727214330.GA1694@britannica.bec.de> References: <1216910072.2251.8.camel@jill.exit.com> <200807251802.23984.lists@jnielsen.net> <1217120187.37762.7.camel@jill.exit.com> <5f67a8c40807271423t3dc1e89bn7295b9af9fa0eda5@mail.gmail.com> <20080727214330.GA1694@britannica.bec.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 27, 2008 at 5:43 PM, Joerg Sonnenberger <joerg@britannica.bec.de > wrote: > On Sun, Jul 27, 2008 at 05:23:46PM -0400, Zaphod Beeblebrox wrote: > > That said, an OS-level suspend-to-disk would be an awesome summer-of-code > > project. > > I don't think it is feasible as SoC project without previous knowledge > and interaction with at least the ACPI suspend-to-RAM code (or > alternative the low-level boot code) and VM knowledge (both MI and MD). > I believe it can be done in 3 month though. Actually, the point I was tryinng to make is that the os implemented suspend-to-disk doesn't need any knowledge of ACPI or any other dependancies. VM knowledge, yes. Some inventive design for (re) opening file handles and other system resources... but the mess that is ACPI doesn't seem to be needed for this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40807271540m3e1354d8s4e8d10e7f101afac>