Search results

Those things are so annoying to pull apart without the stupid inner bezel crumbling to pieces. Don't forget the speaker foam surrounds!

What's missing is called a DAA (Data Access Arrangement). It'd have looked somewhat like a PhoneTalk adapter box.

Stuff that has its own FCode (i.e. PCI cards) gets dynamically loaded into the tree, but the rest of it is static. OpenFirmware doesn't probe each bit of the machine to build a list of things it sees, the device tree was generated at the time the firmware was built. That is, Apple omitted the...

IIRC Apple schematics for PowerBook G4s mention Apollo (7447 is A7, 7448 is A8 - not sure if this applies to 40/45/50/55) not supporting anything 60x. Will be looking at my schematics to see if anything describes UniNorth MPX straps. I think I have a TiBook one that does. @herd nice work on the...

Ha. Yeah, as predicted, you don't have sound under i2s. .properties is a separate command, to be entered on a new line, after typing dev (device name) and hitting enter, which is why you got no response. psuedo(sic)-sound is probably just an entry that exists to initialize the driver that the...

7440 and up are not pin-compatible with 750/7400. It would take an interposer, which some companies briefly sold, and is a pain+costly to recreate. And changes to the VRD.

He probably won't have /pci@xxxx/.../sound, but finding the i2s bus is a good start. dev / ls dev /pci@... dev i2s... until you arrive at the end of the chain. You can issue a ".properties" (with the dot, no quotes) at each level to see the details. Note absence of slashes on entries beyond...

As promised, iBook device tree dumps. The DAC3550 lives at /pci@f2000000/mac-io@17/i2s@10000/i2s-a@10000/sound Also attached are the . properties for each subdevice in this configuration. Sorry for the crappy images, but this iBook's panel is on the way out with vinegar syndrome.

Toss at your favorite PCB service, fabbing at the default 1.6mm is fine - the dumbest PCB ever, it's just holes. This should make re-crimping easier - break/cut to size if you wish, place against pins, stab spacer+board+cable+clamp into vise, squeeze tight. It's got copper around the holes...

I'd say so. Crimping was made less sketchy by placing a spacer (borrowed from a discarded thinkpad drive bay flat PCB) over the pins on the solder side, so I was applying pressure on a flat surface. I suppose I could knock out a PCB insert real quick and publish it here before people attempt to...

Correct, an evolution of. What an 040 is to a DIP m68k.

Re: 5300 vs 500 series performance complaints - one machine came with a bargain basement IDE drive kludged onto what is essentially half of its predecessor design; which is the other, natively equipped with SCSI ;) Laptop SCSI drives were never any marvel, but laptop IDE drives until the 00s...

I've redone the interconnect cable before - releasing the latches without breaking them is the hardest part. You can use UDMA-2 (80way) cables.

Correct, blue is a thermistor. What does the IDPROM handle, you ask? Just battery ID checking. "This is an Apple battery, S/Nxxyyyyy". If that much. I've forgotten the details, can peruse my notes at some other point.

If it's anything like PBDuos, the 3-pin package is not a BMS, just a Dallas IDPROM. The only battery management is a thermistor.

I'd not poke it. A stuck pixel in an active matrix screen is a faulty transistor. There's no science backing any "fix" technique that involves physical contact - most likely result is delaminating the panel and ending up with a black splotch over many pixels.

I would assume Max is using SprintPCB, as that offers trace-over-background functionality.

Like Egret/Cuda and friends, EMM is presumably a 68HC05E1. I have the board somewhat disassembled with values noted down, but haven't actually started on reverse engineering it. You can check for the basic things as in "it's getting power to the right pins" (Vddsyn being power to the on-chip PLL...

A few of us, I would think, agree that the IIci/cx is the turning point where Apple got the design right for a mostly one-size-fits-all computer. They have good basic features, are expandable in a few ways, were not eye-wateringly expensive (looking at you, IIfx), etc. It's not the fastest Mac...

The area around C10 and friends is a bit cruddy, not sure if enough to stop the machine working, but D5, Q3, UD13 and UE13, and the vias around them could all use some retouching with fresh flux. For the two HC132 I'd actually pull them to ensure you have no corrosion issues under the ICs.