Date: Thu, 1 Jun 2006 12:01:57 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "John Baldwin" <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, kylin <fierykylin@gmail.com> Subject: Re: misc questions about the device&driver arch Message-ID: <5f67a8c40606010901s520c8898udf3a254e7f15a7b3@mail.gmail.com> In-Reply-To: <200511061007.03634.jhb@FreeBSD.org> References: <87ab37ab0511032030o134b9316j83295dd303e4e44b@mail.gmail.com> <20051105.140416.69987626.imp@bsdimp.com> <87ab37ab0511060314m2eef7458vefc4f5f657ea6501@mail.gmail.com> <200511061007.03634.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/6/05, John Baldwin <jhb@freebsd.org> wrote: > > > No, FreeBSD doesn't currently do what this decribes yet. It would be > possible > to do it by adding a new device_pause() method that drivers would be > required > to implement while the resources were shuffled around though and possibly > a > device_unpause() method so that they could update their state if their > resources were changed while the device was paused. Commenting specifically on this little nugget, this sounds like a boon to someone that might try and implement a suspend to disk system in the kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40606010901s520c8898udf3a254e7f15a7b3>