Date: Wed, 03 Apr 96 12:11:13 PST From: "Brett Glass" <Brett_Glass@ccgate.infoworld.com> To: Terry Lambert <terry@lambert.org> Cc: terry@lambert.org, bde@zeta.org.au, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Hacked kernel with option to disable "green" mode Message-ID: <9603038285.AA828559516@ccgate.infoworld.com>
next in thread | raw e-mail | index | archive | help
> Uh... because it's impossible to offer the spindown disabling safely > in a drive/controller independent fashion? Why is this impossible? If the flag is set and the drive is not positively identified as one we know how to deal with, the code can simply print a message and continue. > The 0xFB for the Seagate is not the same as is used by all other "green" > hard disks, if they even support it in the first place... True. That's why the command should be issued only in the case where the drive has been identified. > That's the problem... it can't ensure this because you can't send the > command reliably. Why not? Again, the above approach would handle the odd cases. > But you can reliably recover from a spin-down, if your disk driver > has been written correctly. Perhaps. But it may still be desirable (in fact, necessary!) to disable spindowns to get adequate performance. Therefore, FreeBSD should offer this option. > So the generic soloution must be to recover from spindown, not to > disable it. I half agree. Recovery from spindown is important for laptops and other situations where one might like to conserve power. Turning off spindown is important to allow reasonable performance on the desktop and in multi-user situations -- and is ABSOLUTELY NECESSARY until graceful recovery from spindown is possible. BOTH should be implemented. I'd be glad to do work on recognition code that makes the latter safe and adaptable to many brands of drives. --Brett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9603038285.AA828559516>