Final cleanup of OpenMoko Neo1973 kernel patches
I'm doing one final review+cleanup iteration for the OpenMoko Neo1973 GTA01
related kernel patches before pushing them for review later tonight or at some
The cleanups are mostly dead code removal, avoiding compile-time warnings as
well as cosmetic cleanups such as adding MODULE_DESCRIPTION to all modules,
and using consistent naming for files and driver names.
GTA02 will have to wait a bit more. On the one hand, changes that the kernel
developers want me to do on PCF50606 will likely appear in the PCF50633 driver,
too. On the other hand, the entire Smedia Glamo driver core has not been
Playing around with the HTC TyTN II / Kaiser
For reasons that I cannot yet disclose, I have obtained a HTC TyTN II (aka
Kaiser). This is my first (and hopefully last) Windows Mobile based device.
So far I've taken the device fully apart, unmounted all the shielding covers
and took high-resolution photographs of each and every part of the phone.
The resulting information is now that I'm aware of all the major components in
the device, and I've started to do some data mining on those components.
As everyone knows, HTC used a Qualcomm MSM7200 based chipset in this device.
The MSM integrates both the GSM baseband (DSP+ARM9) as well as the application
processor (ARM11) and many other things. What's less known is the further
- The Bluetooth and WiFi chips are from Ti (BRF6300 and WL125, respectively).
- The power management unit is a Qualcomm PM7500
- NAND+DRAM are in a multi-chip module (1.8V, 2GBit NAND x8, 1GBbit DRAM x32) from Samsung
- The 3G/GSM RF part consists of Qualcomm's RFR6500 (receive with integrated GPS) and RTR6275 (transmit) as well as AWT6280, AWT6273 and AWT6273 amplifiers
- There furthermore is a CPLD: Xilinx XC2C128 (3000 system gates, 128 macrocells).
For those interested, I'll go through my PCB photographs and will edit and
publish them soon.
I am now digging through all the various XDA/WM6 hacker information out there
and trying to understand the various tools that can be used for further taking
apart the software side. I've already managed to get into the bootloader,
which apparently offers a standard USB serial emulation that can be accessed even from a Linux PC.
Unfortunately the MSM7200 is a highly proprietary/closed chipset, and there is
very limited public information available. I've already ran into this while
evaluating potential hardware for OpenMoko at some point in the past. I became
curious about this MSM7xxx chipset family when they were first added to the
ARM-Linux machine type registry many months ago.
Anyway, meanwhile Google seems to be doing a lot using this chipset, as they
have recently announced the availability of a linux-msm.git tree. The source code should document many things such as GPIO assignments, IRQ's and contain drivers for most of the hardware (on the application processor side).
Now if some of you ask yourselves if I have turned my back on OpenEZX and
OpenMoko: No, that's not true. I'm just looking at this for a very peculiar
reason. Hopefully I'm able to reveal more soon.