That thought had crossed (what little is left of) my mind, but in doing so, you'd remain shackled to a newer "closed system" and what I've got in mind is an "open source" hardware/software hack project! [

] ]'>
I hate to say it, but I think it's about this point I start losing the plot... oh, okay, I see scrolling back a reference to some embedded ARM board. It gets *really* confusing because at some points you're talking about "hijacking" busses on a Powerbook Duo motherboard or cramming a new CPU into it, and at other points you're, uhm, talking about replacing the innards with some other board, but somehow continuing to use a DuoDock interface for... something? (No, wait... you want that ARM board to somehow substitute for the PBX IC on the motherboard...?) And I'm really confused how "Ubuntu" and "Open Source" gets mixed up into this.
(I don't think you're going to find oodles of wide-ranging enthusiasm out there for an "open source hardware project" that's somehow dependent on hacking up obscure 12 year old *highly proprietary* laptop computers. It's sort of silly to call a Netbook a "closed system" by comparison. The IBM PC platform has evolved into the epitome of an "Open Platform", able to cover applications from matchbox-sized embedded devices to supercomputers, and even a humble $300 Netbook is bristling with modern expansion capabilities. Generally at least two of them (USB Ports). However, if you really need to do something *weird* most Netbooks use a Mini-PCIe slot to connect their wireless module. A
nearly passive adapter card can adapt Mini-PCIe to full-size PCIe, and
Magma and others can sell you PCIe-to-PCIe or PCIe-to-classic-PCI expansion chassis. It'd be stupidly expensive to cobble together compared to just using a PCI/PCIe desktop motherboard for your weird real-time-high-speed-bus-requiring hack project, but it's *very doable* with hardware bought right off the shelf.)
I think you need to type up a whitepaper including a few illustrations and a block diagram. Or at least take a photo of a whiteboard with your idea on it. My poor primitive brain has really run off the rails trying to grok what you have in mind. Is this all one grand project or a bunch of unrelated ideas getting hopelessly smashed into psuedotechnical goo?
(At this point Jordi LaForge shows up and starts hollering something about tachyons flooding the warp overdrive conduit manifold and causing a cascade blawblawblawTECHTECHTECH... No, wait, reading back again I see there *was* a bifurcation point where it became "new guts Duo body"... but then it went back to G3s and "substitute this board for the "PBX IC"....
And on that subject, I have to admit I really don't understand the strange obsession with "fast side/slow side" on this thing. Sure, if you're interfacing RAM you want all you can get, which I guess means you want to be on the "fast" 33Mhz/64 bit side, but for *just about any* conceivable homebrew peripheral 25Mhz/32 bits should do just grand. One of my coworkers is constructing his own 3D CNC milling machine, and all he needs to control 3 stepper motors in real time is a simple IBM PC parallel port. Which is a lot slower then the PBX IC's "slow side".
The only thing "wrong" with the PBX IC is it has a 56MB RAM limit, which was probably a reasonable number when the Duo was new. It wasn't some evil limitation put there to forever irk mankind. It just... is what it is. I don't see many owners of 1967 MGB Midgets complaining that they can't drive 500 miles per hour while carrying a couple dozen tonnes worth of bulk cargo in the trunk. If you need to actually do those things simultaneously you're not in the market for a tiny sports car, you're shopping around for a good deal on a used 727 freighter conversion. You can say the same thing about all the other "dated/limited" components in the Duo. The whole thing was a compromise between cost, weight, size, and the available technology. If you don't like the formula it's probably sort of pointless to try to "fix" it even if you're enamored with the aesthetics.)
The point of the
ubuntuCentricDuoHack™ is to build a carrier board to knit together an easily interfaced I/O traffic cop (self booting into Linux) SBC and a much more powerful CPU card. The Duo MoBo/Expansion Card form factor “carrier board” would retain ONLY the Duo's CONNECTORS for Power, a totally revamped battery, something
new and exciting running on a DIN-X (or a newer round connector of similar size) where the serial port was,
possibly RJ-45 (or something REALLY Sexy) where the Modem Connector was and only the physical Docking Connector itself, outfitted with
an all new set of modern interface signals from the I/O traffic cop. (similar to the two Apple II Procs doing I/O Co-Processing in the Iifx! [

] ]'>

BTW, one might also load an LVDS (?) driver board into the FPGA section of said I/O traffic cop! }
Okay... and this is all going to be better than a simple, clean replacement motherboard... how? Never mind. Sounds AWESOME. Just don't expect it to perform any better than a simple, clean replacement motherboard. If what you really want is an ARM CPU'ed laptop running Ubuntu
supposedly a tidal wave of them should be available "any day now". They're not going to perform better than Atom netbooks but they should eek out more battery life. At the cost of binary software compatibility, of course, which may or may not matter.
If you find an LCD panel that has enough pixels for you and fits in the space occupied by the Duo's LCD there are *oodles* of both ARM and x86 embedded motherboards that should fit in the available space in the Duo case and have LCD drivers onboard. (Beware, however, the video controllers in most ARM hardware tends to be "PDA-centric" and tops out at fairly low resolutions.) The suggestion about using the guts of a laptop instead of an SBC mostly comes from the fact that stripping down an existing laptop will probably be cheaper than a custom embedded board once you factor in finding all the bits to make it really "go". (Another advantage is a laptop will come with a BIOS which supports intelligent battery power management, something you'd have to homebrew otherwise.) A single integrated motherboard, whether it's from a laptop or an industrial SBC, should do what you want much more easily than running down some strange cobbled-together-from-mismatched-bits rathole, which is what "traffic cop SBC plus powerful CPU card!" sounds like to me.
But I guess if running down a rathole is the whole point, then, uhm... squeak!
Absolutely, and a hearty welcome to the ranks of the 68kMLA, eudi! [

] ]'>
BTW, I know some folks in the “war room” who can fix up your nom-de-guerre probs if you should wish to have it done? [

] ]'>
I could go either way. As long as it's primitive, toothy, bad-tempered, and has a tiny brain either avatar suits me fine. ;^)