Ian Murdock wrote: > > The most obvious missing feature is suspend and resume. I've heard > there are people working on this.. What's the status of this work, > and is it something we'll be able to use in the October timeframe?
> I wonder about battery life. Presumably, this is related to the other > power management work (scaling back the CPU when idle etc.) (posting to tesla-dev so that Randy Fishel and Mark Haywood can comment here). Mark is working on the frequency / voltage scaling mechanisms, and Randy is working on suspend / resume. > Desktop responsiveness could use some work. There was a lot of > work done in the Linux kernel a few years ago to improve this on > Linux, and it made a world of difference there.. I computed an > md5sum last night on an ISO image, which degraded desktop > responsiveness pretty badly. And while audio works beautifully compared > to Linux in how it multiplexes multiple streams, it's pretty jittery > from time to time, presumably due to scheduler prioritization > (not prioritizing interactive tasks ahead of non-interactive tasks). The timeshare scheduling class should be doing the right thing here. The more CPU bound md5sum should tend to have it's priority drop, while the more transient interactive tasks should have their priorities increase. So it might be that the jitter is related to something else, but it should be fairly straightforward to suss out with dtrace(1M) and friends. I can take a look. > The buttons (disable/enable wireless etc.) don't seem to do anything. > Those just generate ACPI events, so presuming there's some way for a > user-level process to monitor those events and dispatch the right action > (e.g., bring the wireless interface down/up), that shouldn't be hard. > On Linux, there's a user-level daemon called acpid that does this. Not > sure what the Solaris equivalent is, or even of the state of ACPI > support. The hard part here is undoubtedly making sure the right codes > for a variety of laptops are recognized, and that's something a larger > user community can help us get right over time (that's how Ubuntu > did it--very little of this worked at the beginning, but it improved). Dana? :) Thanks, -Eric
