On 2003-01-23 at 03:57:09 (+0100), Carlos A. Paramio wrote:
> On Wed, Jan 22, 2003 at 12:03:35PM -0500, Nathan J. Williams wrote:
> > Power management pretty much consists of CPU temperature measurement,
> > battery/line measurement, and disk spindown. There's no sleep/suspend
> > or screen dimming/blanking.
> 
> OK... sleep/suspend possibilities are not as important as the others
> for me, but it would be good.

If this iBook utilizes the 750FX G3 cpu produced by IBM, like the ones
in the previous iBook from 2002, then there is even possible to reduce
cpu-frequency without much work. This is just done in 3 lines of
assembler code. Mac OS X even shuts down some part of (or the whole???)
branch unit which causes less power consumption. I played a bit with it
on netbsd 1.6 - it works very well, it's even possible to switch
cpu-frequency in the running system. But I don't know if there are some
timers which will get confused by this or don't work properly then.
Don't run it primary.

But I have another question:
Someone tried to get X11 working on iBook early/summer 2002 with Radeon
Mobility LY (M6)? I had problems with it trying to get XF4.x running.
Tested from cvs xsrc, cvs xfree86, some prebuild driver posted to this
list. The best result I got was the 1024x768 resolution streched, so
that only a part (around 80%) was shown (looked like the driver is
thinking there is a 1280x960 or something display connected). So the
screen looks very ugly, because it is scaled and I don't see anything.
Someone knows some good solution for this?

> 
> > The modem on older models can be made to work with a patch. Newer
> > models appear to have a software-DSP modem that we don't support.
> 
> I expect that. No problem because all my "outworld" connections are
> through ethernet (and wireless in a near future).
> 
> > Audio doesn't work. The information is out there, more or less, but
> > nobody's written the driver. I've been using a Griffin iMic when I
> > really needed audio.
> 
> That's a real problem for me! However, I'll try to install NetBSD
> so I can test it, now I know almost devices are supported. Is it really
> difficult to write a driver for NetBSD, for a person who has a good C
> level and computer science knowledges? I never tried to make one, of
> course! :-)
> I suppose a lot of documentation about NetBSD kernel structure
> and the device itself must be readed.
> 
> Thaks for your help,
> -- 
> Carlos A. Paramio
> carlosparamio@ono.com
> http://webs.ono.com/carlosparamio



-- 
Gruss
  Matthias Kretschmer