Thanks,
But no, this isn't the case on the Zaurus.
The hw.cpuspeed sysctl is a read only value.
The machdep.maxspeed was introduced to scale up and down the hw.setperf
parameter on this system.
The Zaurus normally operates at 416Mhz, the sysctl.conf contains the line
machdep.maxspeed=520 on the Zaurus.
I was going to set the maxspeed at that (worked on previous kernels) and the
setperf value at 80 and vary it to 100 when I was running a build (along
with atactl /dev/wd0c writecacheenable - I'm using a SanDisk Ultra III which
provides write cache, can't remember if the Microdrive did).
Any more thoughts folks?
-Andy
----- Original Message -----
From: "Chris Kuethe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 10, 2007 4:51 PM
Subject: Re: Changes to sysctl mibs recently?
i think you might belooking in the wrong place... my zaurus is at home
right now, but on every other machine i have with adjustable cpu speed
the controls are hw.cpuspeed and hw.setperf.
CK
On 8/10/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Hi,
I'm wondering if anyone can tell me about any recent changes in the
sysctl mibs.
I notice that the current snapshot on my Zaurus doesn't seem to handle
machdep.maxspeed any more and just says 'value is not available'.
OpenBSD 4.2 (GENERIC) #158: Wed Aug 8 15:32:05 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/zaurus/compile/GENERIC...
etc.
I also built a kernel and a new copy of sysctl from CVS and this doesn't
seem to fix it either (although I haven't built the whole distro yet)
sysctl machdep seems to report only..
midge# sysctl machdep
machdep.debug=0
machdep.console_device=ttyC0
machdep.allowaperture=0
machdep.apmwarn=10
machdep.kbdreset=1
machdep.radix=0
Any ideas?
-Andy
--
GDB has a 'break' feature; why doesn't it have 'fix' too?
