On Tue, Sep 02, 2008 at 02:52:17AM +1000, Finn Thain wrote:
On Mon, 25 Aug 2008, Brad Boyer wrote:
On Mon, Aug 25, 2008 at 05:11:55AM +0200, Michael Schmitz wrote:
... please check whether they support the common battery state
response formats as well, and perhaps sleep messages? :-) I'd even add
support for m68k powerbooks to pmud if possible ...
I'll try it out on the PB190 when I get a chance, but I'm much more
worried about the older models for this sort of thing. Does anyone have
anything old enough for the driver to claim it has a "V1" PMU? That
would be any PB1xx other than the PB190.
Yes, I have some. I've revived a 170 (which is one of the earliest
models), a 145 and a 150. What do you want me to test for?
There are a couple extra PMU commands that the via-pmu.c driver uses
that aren't used by via-pmu68k.c, with the chip version query being
the most relevant one to this discussion.
J's kernel works OK with the PMU chip in my PB 150 (see log below). I also
tried it on a Duo 280c, but it usually shuts the screen down when the PMU
driver loads but not always (see log below). That doesn't stop ADB from
working correctly however. I can also test a Duo 230 if need be.
That's good to know. The 150 is fairly old and would be likely to be more
similar to the PB100 (not that we support the 100) than the PB190.
BTW, to revive these things I had to remove the PRAM battery. It appears
that a worn out battery will prevent them powering up. Some of the
batteries were leaking (as were some of the main batteries). So, a word of
advice: remove them or leaking battery acid will eventually destroy the
circuitry. I've seen it happen to a Mac IIsi motherboard.
I guess I should open up my PB190. It has a broken trackpad button anyway,
which I should try to fix.
Thank you for the two debug output dumps. I see they both do the pmu intr 00
as well. It sounds like the 190 is about the only model that doesn't do it.
Brad Boyer
flar@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
